FS_MCP_thin

Get Requester

get_requester

Retrieve complete requester information by ID. Get requester details to enrich ticket triage and support history analysis.

Instructions

Retrieve full details of a specific requester by ID

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": {
      "requester_id": "<requester_id>"
    },
    "name": "get_requester"
  }
}

Input Schema

Name	Required	Description	Default
`requester_id`	Yes	The requester ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It only says 'Retrieve full details' without mentioning authorization requirements, error behavior, response format, or any side effects. For a getter, one might assume read-only, but the description itself does not confirm this or other important behavioral context.

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

Conciseness5/5

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

The description is a single, concise sentence that immediately conveys the action and the resource. It is fully front-loaded with no filler or redundant phrasing.

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 simple one-parameter getter, the description is mostly adequate, but the phrase 'full details' is vague and no output schema exists. The description does not specify what fields or response structure to expect, leaving some ambiguity about the tool's return value.

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

Parameters3/5

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

The input schema already provides complete documentation for requester_id at 100% coverage, so the description need not add parameter details. The description's mention of 'by ID' aligns with the schema but adds no new semantic information beyond what is already in the structured data.

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

Purpose5/5

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

The description clearly states the verb 'Retrieve' and the resource 'full details of a specific requester,' with the qualifier 'by ID' that distinguishes it from search_requesters and other requester-related tools. This is a specific and unambiguous purpose.

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

Usage Guidelines3/5

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

The description implies the tool should be used when a requester ID is known, but it does not explicitly mention alternatives like search_requesters or get_requester_tickets, nor does it state when not to use it. Sibling tools exist, but no exclusions or comparisons are provided.

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