JIC

Ask the JIC reception agent

jic_ask

Read-only

Ask one question in any language about JIC: rules, money, a specific site, what to do first. The reception agent is an AI that answers from a fixed brief plus live data. It explains and points; it cannot sign, pay or join for you.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "question": "<question>"
    },
    "name": "jic_ask"
  }
}

Input Schema

Name	Required	Description	Default
`question`	Yes	Your question, at most 2000 characters

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, non-destructive, and closed-world. The description adds meaningful behavior beyond that: answers come from a fixed brief plus live data, the agent only explains and points, and it cannot perform transactions. This helps set expectations for answer quality and limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the action and topics, followed by agent behavior and limits. No wasted words, though the middle sentence about the AI could be tighter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter Q&A tool with no output schema, the description covers what it does, how it answers, and what it cannot do. It omits return format, but that is reasonably expected as a text answer and the annotations cover the safety profile.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is self-explanatory. The description still adds value by noting that questions may be in any language and by giving topic examples, which broadens understanding beyond the schema's length limit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb (ask one question) and resource (about JIC: rules, money, sites, first steps), and explains that this is the reception agent. It does not explicitly name sibling tools, so differentiation is slightly weaker than a 5, but the agent's role is clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It lists the kinds of questions to bring here and explicitly excludes signing, paying, or joining, which implies those actions belong to other tools. No named alternatives, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All JIC tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?