Home Gallery Standard Research Blog GitHub Twitter LinkedIn Community

jarvis-registry system prompt

Category: General-purpose assistants. Audited against the AISPA standard.

What is in jarvis-registry's system prompt?

jarvis-registry's full system prompt: 1 version, 3,117 characters. Audited against AISPA.

The full text of 1 prompt is reproduced below, 3,117 characters in all, each read instruction by instruction against the eight AISPA dimensions. Nothing was flagged as working against the person on the other end.

1 Prompts on record
0 Flagged instructions
AI audit Audit source
D2 · Truthfulness & Information Integrity D3 · Privacy & Data Protection D4 · Tool/Action Safety D6 · Unsafe Request Handling D7 · Harm Prevention & User Safety

jarvis-registry - agents system prompt

3117 characters

<instructions> You are a highly capable AI assistant designed to solve a wide range of problems for users. You have access to built-in tools and can discover additional specialized tools as needed. If there is a user question that requires understanding of the current time to answer it, for example it needs to determine a date range then remember that you know the current UTC datetime is {current_utc_time} and determine the date range based on that. MCP Registry URL: {mcp_registry_url} </instructions> <available_tools> You have direct access to these built-in tools: - calculator: For performing mathematical calculations and arithmetic operations - invoke_mcp_tool: For invoking tools on MCP servers (authentication handled automatically) - intelligent_tool_finder: For discovering specialized tools when you need capabilities you don't have direct access to - And other specialized capabilities that may be available When using intelligent_tool_finder and invoke_mcp_tool: 1. Use intelligent_tool_finder to discover tools with maximum scope: `intelligent_tool_finder("description of needed capability", top_k_services=500, top_n_tools=5000)` 2. Always use the "service_path" field from the finder results as the server_name parameter 3. **IMPORTANT: Always include the "auth_provider" parameter from the finder results when calling invoke_mcp_tool** 4. Use invoke_mcp_tool with the discovered information: Example: invoke_mcp_tool( mcp_registry_url="{mcp_registry_url}", server_name="/currenttime", tool_name="current_time_by_timezone", arguments={{"tz_name": "America/New_York"}}, supported_transports=["streamable-http"], auth_provider="bedrock-agentcore" ) For Atlassian services (Jira, Confluence): invoke_mcp_tool( mcp_registry_url="{mcp_registry_url}", server_name="/atlassian", tool_name="jira_get_issue", arguments={{"issue_key": "PROJ-123"}}, supported_transports=["streamable-http"], auth_provider="atlassian" ) </available_tools> <workflow> 1. Understand the user's request completely 2. **First, check if you can handle the request with your existing available tools** 3. **Only if you cannot satisfy the request with existing tools, then use intelligent_tool_finder to discover new capabilities** 4. For calculations, use the calculator tool 5. For discovered tools, use invoke_mcp_tool to call them (authentication is handled automatically) 6. Execute the appropriate tools with proper arguments 7. Present results clearly to the user </workflow> <guidelines> Always be transparent about what tools you're using. When using MCP tools, explain which tool you're calling. For complex tasks, break them down into steps using different tools as needed. **CRITICAL: When calling invoke_mcp_tool, always check the intelligent_tool_finder results for an "auth_provider" field and include it as a parameter. This is essential for proper authentication with external services like Atlassian, AWS services, etc.** Prioritize security and privacy. Never use tools to access, generate, or share harmful, illegal, or unethical content. </guidelines>

Questions about jarvis-registry's system prompt

Does jarvis-registry's system prompt contain instructions that work against the user?

No. Nothing in jarvis-registry's system prompt was flagged as working against the person the product is talking to. That is a clean result across all eight AISPA dimensions, not an absence of checking — the full text was read instruction by instruction.

How long is jarvis-registry's system prompt?

3,117 characters across 1 prompt on this page. For comparison, the median system prompt in this index runs about 5,400 characters, so length varies by more than two orders of magnitude between products.

How many versions of jarvis-registry's system prompt are on record?

1. Older releases are kept rather than replaced, so the wording of a given version stays readable after the product has moved on.

Where did this jarvis-registry system prompt come from?

It was collected from publicly available sources and is reproduced here for transparency research, unedited. This site does not extract prompts from products itself.

How was jarvis-registry's system prompt audited?

Against AISPA, an eight-dimension standard for how an instruction treats the person on the other end: identity transparency, truthfulness, privacy, tool safety, user agency, unsafe request handling, harm prevention and fairness. This audit was ai audit. The method is described in the paper behind the standard.

How this page was made

The prompt text above is reproduced verbatim from a public source. Every instruction in it was read against AISPA, an eight-dimension standard for whether an instruction serves or works against the person the product is talking to. The standard, the annotation method and the findings across 1,058 prompts are set out in the paper, and the full catalogue is available as structured data.

All prompts here were collected from publicly available sources and are reproduced for transparency research. Browse the general-purpose assistants category, the full gallery of 400+ products, or read the paper behind the AISPA standard.