FS_MCP_thin

Get Problem

get_problem

Retrieve complete details of a problem record by its ID, delivering the full information needed to analyze issues and track resolution progress.

Instructions

Retrieve full details of a specific Problem record

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": {
      "problem_id": "<problem_id>"
    },
    "name": "get_problem"
  }
}

Input Schema

Name	Required	Description	Default
`problem_id`	Yes	The problem ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A3.8/5.0

Behavior3/5

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

There are no annotations, so the description must carry the behavioral burden. The description indicates a read operation ('Retrieve') and says 'full details' but does not disclose return format, error handling, or permissions. Since this is a simple read, it is minimally adequate.

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?

One concise sentence with no filler, effectively front-loaded.

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 simple retrieve operation with one parameter, the description is adequate. However, without an output schema, it could clarify what 'full details' includes, though the context makes it predictable.

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 schema provides a complete description for problem_id (type number, required). The description's reference to 'specific Problem record' confirms the parameter's role but adds no additional semantic detail beyond the schema, so baseline 3 applies.

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 uses the verb 'Retrieve' and identifies the resource as 'a specific Problem record,' clearly distinguishing it from list_problems and other get_* tools targeting different entities.

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?

No explicit guidance on when to use this tool versus list_problems or other tools. The phrase 'specific Problem record' implies it requires a known ID, but no alternative tools are mentioned or excluded.

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