Skip to main content
Glama

Get Wanted

get_wanted
Read-onlyIdempotent

Get the full FBI Wanted profile for one person by uid, physical description, aliases, occupations, caution/remarks/details (plain text), reward, field offices, and images. Keyless, official FBI data.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "uid": "1234567"
    },
    "name": "get_wanted"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYesThe wanted-person uid (from search_wanted / most_wanted results).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety behavior is covered. The description adds two pieces of real value beyond them: "Keyless" (no auth or API key required) and "official FBI data" (source provenance and reliability). It says nothing about how a not-found uid behaves or whether results reflect live versus cached data.

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 short sentences: the first front-loads the verb, resource, and the full field inventory; the second carries the keyless/provenance qualifier. Every clause earns its place with no filler or repetition.

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 one-parameter, read-only lookup with no output schema, the field enumeration (physical description, aliases, occupations, caution/remarks, reward, field offices, images) effectively substitutes for a return-value schema. What is missing is edge-case behavior for an invalid or unknown uid, which is a minor gap for a tool this simple.

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

Parameters4/5

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

Schema description coverage is 100% and the single uid parameter is documented with its source (search_wanted / most_wanted results), so the baseline is 3. The description reinforces this by framing the call as a per-person lookup keyed on that uid, though it adds no format, length, or validity detail 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 names a specific verb and resource ("Get the full FBI Wanted profile for one person by uid") and enumerates the returned sections: physical description, aliases, occupations, caution/remarks, reward, field offices, images. This clearly separates it from the list-style siblings search_wanted and most_wanted in behavior, though those alternatives are never named in the description text itself.

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?

Usage is only implied: "for one person by uid" signals a detail/lookup call versus a search, and the schema hint mentions the uid comes "from search_wanted / most_wanted results." There is no explicit when-to-use or when-not statement, no precondition around obtaining a uid first, and no error guidance for a missing or stale uid.

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.