Skip to main content
Glama

Veyrul media knowledge hub

Private resident assistance (unavailable)

request_resident
Idempotent

New private hosted advice is currently unavailable. Use get_context or post a public community question; replies are capped and not guaranteed. Existing requests remain readable/cancellable under their original permissions. This retained endpoint does not authorize new model execution.

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": {
      "input": "<input>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "request_resident"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
idempotency_keyYesRequired. Retry this exact mapped REST request with the same key for 24 hours; no duplicate work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Adds real context beyond the annotations: replies to the redirected path are capped and not guaranteed, existing requests stay readable/cancellable under original permissions, and this endpoint does not authorize new model execution. The annotations declare idempotentHint and openWorldHint, and the description complements rather than repeats them. The one gap is that it never says what a call to this endpoint now produces, which matters for a non-read-only tool.

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?

Four short sentences, with availability status and alternatives front-loaded and no filler. Each sentence carries distinct information (status, alternatives, survivors' permissions, no new model execution), though the last two overlap slightly in emphasizing the endpoint is inert.

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

Completeness3/5

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

For a deprecated endpoint with no output schema and a heavily nested 2-parameter input, the description covers status, alternatives, and permission constraints, which is the important part. It is still missing the expected call outcome and any parameter-level caveats for the nested object, which an agent would need before deciding whether to attempt a call.

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

Parameters2/5

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

Schema coverage is only 50%, with just idempotency_key documented in the schema; the nested input object (request, role, report_id, record_refs, context_subset, model_permission, parent_request_id) has no field-level descriptions anywhere. The description says nothing about any parameter, so the agent gets no guidance on, for example, whether model_permission or context_subset are even honored by a retained endpoint.

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

Purpose3/5

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

The description front-loads that the private hosted advice capability is unavailable and that this is a retained endpoint, which tells an agent what the tool is in its current state. It never states what the tool actually returns or does when called — error, no-op, or read of prior state — so the operational purpose remains ambiguous beyond the name and title.

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 explicitly routes the agent away from this tool to named alternatives (get_context, or posting a public community question) and warns that replies are capped and not guaranteed. It stops short of a hard 'do not call' instruction or explaining the conditions under which this endpoint should still be invoked.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources