Skip to main content
Glama

Who does one job, and why

get_use_case
Read-onlyIdempotent

One use case from find_niches: what counts as done and every listing's mark (yes, caveat, no, unchecked) with a reason and source.

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": {
      "id": "<id>"
    },
    "name": "get_use_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA use-case id, e.g. gpu-compute.serverless-model-endpoint

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare a safe, read-only, idempotent operation. The description adds useful return-content detail by naming the completion criteria and listing mark statuses with reason and source, though it does not mention invalid-id behavior.

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?

It is a single dense sentence with no wasted wording and front-loads the resource plus returned information. The phrasing is slightly compressed but remains understandable.

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 one-parameter read tool with rich annotations and no output schema, the description sufficiently explains what is returned. Only edge-case behavior for invalid ids is left implicit.

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 coverage is 100% and includes an example id format, so the schema carries parameter semantics. The description adds only the context that the id refers to a use case from find_niches, which is marginal 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 identifies a specific resource: one use case from find_niches, including completion criteria and each listing's mark. It distinguishes the tool from find_niches, though it implies retrieval rather than stating it with an explicit verb.

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?

Referencing find_niches implies this tool is used to inspect a use case discovered there, but it gives no explicit when-to-use guidance, prerequisites, or when-not-to-use alternatives.

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