Skip to main content
Glama

4fillment

Check a case

get_case
Read-onlyIdempotent

The status of a support case opened with ask_a_person: open, answered or closed, and when a person replies. Needs the reference and the access_token that ask_a_person returned.

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": {
      "reference": "<reference>",
      "token": "<token>"
    },
    "name": "get_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesThe access_token ask_a_person returned with that reference.
referenceYesThe case reference ask_a_person returned, e.g. 4F-7KQ2M9XD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful behavioral context beyond annotations by disclosing the required access token from ask_a_person and what status information is returned.

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?

Two sentences with no wasted wording: the first states the returned status information, and the second states the credential dependency. The content is front-loaded and directly useful.

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 two-parameter read-only status tool with annotations covering safety and idempotency, the description is largely complete. It explains the authentication dependency and return statuses, though it could be slightly more precise about what information accompanies a person's reply.

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?

Schema description coverage is 100%, and the two parameters are already well documented in the schema. The description reinforces that both the reference and token come from the ask_a_person response, but it does not add meaningful syntax or usage semantics beyond the schema.

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 clearly identifies the resource as a support case and states that it returns status values (open, answered, closed) and reply timing. It also ties the case to ask_a_person, which distinguishes it from unrelated siblings, though it uses a noun phrase rather than a specific operation verb.

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?

The description makes the usage context clear: this checks a case opened via ask_a_person and requires the credentials that call returned. It does not explicitly state when not to use it or name alternatives, but the workflow dependency is sufficient for correct selection.

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