Skip to main content
Glama

Search Wanted

search_wanted
Read-onlyIdempotent

Search the FBI's Wanted persons database, fugitives, Most Wanted, cyber's-most-wanted, terrorists, white-collar suspects, kidnappings/missing persons, and law-enforcement-assistance cases. Returns compact records with reward, warning, and image. 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": {
      "query": "bank robbery suspect"
    },
    "name": "search_wanted"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1).
queryNoFree-text title search (matches the subject name/case title).
sort_onNoField to sort on, e.g. "modified" (default) or "publication".
page_sizeNoResults per page (default 20, max 50).
field_officeNoFilter by FBI field office, e.g. "miami", "newyork", "losangeles".
person_classificationNoFilter by person classification, e.g. "Main", "Victim", "Ten Most Wanted".
poster_classificationNoFilter by poster/program category. Common values: "ten" (Ten Most Wanted Fugitives), "cyber", "wcc" (white-collar crime), "terrorist", "kidnap" (kidnappings/missing persons), "ecap" (Endangered Child Alert Program), "seeking-info", "law-enforcement-assistance".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "items": {
      +      "description": "List of wanted persons",
      +      "items": {
      +        "properties": {
      +          "description": {
      +            "description": "Brief description of the person or crimes",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "images": {
      +            "description": "Available photos",
      +            "items": {
      +              "properties": {
      +                "caption": {
      +                  "description": "Image caption if available",
      +                  "type": [
      +                    "string",
      +                    "null"
      +                  ]
      +                },
      +                "original": {
      +                  "description": "URL to original image",
      +                  "type": "string"
      +                },
      +                "thumb": {
      +                  "description": "URL to thumbnail image",
      +                  "type": "string"
      +                }
      +              },
      +              "required": [
      +                "original",
      +                "thumb"
      +              ],
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "subjects": {
      +            "description": "Crime subjects/categories",
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "title": {
      +            "description": "Person's name or title",
      +            "type": "string"
      +          },
      +          "uid": {
      +            "description": "Unique identifier for the person",
      +            "type": "string"
      +          },
      +          "url": {
      +            "description": "URL to FBI profile page",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "uid",
      +          "title",
      +          "subjects"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "page": {
      +      "description": "Current page number",
      +      "type": "number"
      +    },
      +    "query": {
      +      "description": "Search query used (null if omitted)",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "total": {
      +      "description": "Total number of wanted persons matching query",
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "query",
      +    "page",
      +    "total",
      +    "items"
      +  ],
      +  "type": "object"
      +}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "query": "terrorism"
      +  },
      +  {
      +    "page": 1,
      +    "query": "James"
      +  }
      +]
  5. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by stating the data is keyless and official, and that results include compact records with reward, warning, and image.

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 two tight sentences with no wasted wording. The core purpose and scope are front-loaded, followed by return-value and access context.

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 search tool with full schema coverage and annotations covering safety and openness, the description is largely complete. It explains data source, access model, and returned fields, though it could say more about pagination or result limits, which are only documented in the schema.

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%, so the input schema already documents all seven parameters, including page, query, sort_on, page_size, field_office, person_classification, and poster_classification. The description does not add parameter-specific meaning beyond what the schema provides, so the baseline score of 3 applies.

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 gives a specific verb and resource: search the FBI's Wanted persons database. It enumerates the case categories covered, which helps an agent understand scope, but it does not explicitly differentiate this search tool from siblings like get_wanted or most_wanted.

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 implied by the word 'search' and the broad database scope, but there is no explicit guidance on when to use this versus get_wanted, most_wanted, or other lookup tools. No exclusions or alternative-selection criteria are stated.

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.