Skip to main content
Glama

Search curators by name

search_curators
Read-onlyIdempotent

Find Steam curators by name. Use it when someone names a curator (for example one that emailed them asking for a key) and you need its Curator Match id. Matching ignores case, spacing and punctuation, and a part of the name is enough. A Steam curator link or id also works. Returns up to ten curators, biggest first, with followers, warning level and links.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe curator's name or part of it, such as "PC Gamer" or "shotgun". A Steam curator link or id also works.

Output Schema

NameRequiredDescriptionDefault
queryYes
matchesYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / name / description
      Added value: +"The curator's name or part of it, such as \"PC Gamer\" or \"shotgun\". A Steam curator link or id also works."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "matches": {
      +      "items": {
      +        "properties": {
      +          "curator_id": {
      +            "type": "integer"
      +          },
      +          "followers": {
      +            "type": [
      +              "integer",
      +              "null"
      +            ]
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "steam_url": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "type": "string"
      +          },
      +          "warnings": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "curator_id",
      +          "name",
      +          "followers",
      +          "warnings",
      +          "url",
      +          "steam_url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "message": {
      +      "type": "string"
      +    },
      +    "query": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "query",
      +    "matches",
      +    "message"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond annotations (readOnly, idempotent, openWorld, non-destructive) the description discloses fuzzy-match semantics (case, spacing and punctuation ignored), that a partial name suffices, that links or ids are accepted, and the result shape: max ten results, sorted biggest first, including followers, warning level and links. That is substantial behavioral context an agent could not derive from the annotation flags.

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?

Four short sentences, each carrying distinct information: purpose, trigger, matching rules, result shape. The most decision-relevant content (what it finds and when to reach for it) is front-loaded with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a single fully-documented parameter, rich annotations, and an output schema, the description covers everything the agent still needs: the invocation trigger, name-matching tolerance, and the cardinality/ordering of results. Nothing needed to call it correctly is missing.

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 coverage is 100% and the schema already states 'name or part of it' and that a link or id works, so part of the description repeats structured data. The addition that matching ignores case, spacing and punctuation gives genuinely new semantic meaning about how the name value is interpreted.

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 opens with a specific verb and resource ('Find Steam curators by name') and states the goal output (Curator Match id), which is far more than a restatement of the title. It never names a sibling tool, so differentiation from get_curator or find_curators_for_games is left implicit to the agent.

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?

'Use it when someone names a curator (for example one that emailed them asking for a key) and you need its Curator Match id' gives a concrete, actionable trigger scenario. It lacks any explicit when-not-to-use or named alternative, so the routing burden on the agent remains partially unmet.

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.