Skip to main content
Glama

Run a search again

runRoleSearch

Start a new run of a Search (roleSearchId from listRoleSearches) to find more people now, instead of waiting for its schedule. If a run is already going, returns that one. Each run uses search credits, so confirm with the user first. Read new people with getRoleSearch.

Clera privately records this tool's inputs and results for usage tracking and support.

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

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
roleSearchIdYes

Output Schema

NameRequiredDescriptionDefault
runIdYes
searchYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false), the description discloses the two behaviors an agent most needs: the action spends credits and therefore needs user confirmation, and concurrent invocation collapses to the in-flight run rather than starting a duplicate ('If a run is already going, returns that one'). It also discloses that inputs and results are recorded for usage tracking and support, which the annotations do not cover.

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?

The operational content is front-loaded in three dense sentences: what it does, concurrency behavior, cost/confirmation requirement, and how to read results. The closing privacy/recording line is boilerplate rather than task guidance and slightly dilutes an otherwise waste-free paragraph, but nothing in the actionable portion is redundant.

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?

For a two-parameter action tool with an output schema, the description covers everything needed to invoke it correctly: the ID's provenance, the org scoping caveat is left to the schema, the cost gate, the concurrency semantics, and the next step for consuming results. Return values need not be explained because an output schema exists.

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 50%: orgId is documented in the schema, while roleSearchId only carries UUID format/pattern there. The description fills that gap by naming listRoleSearches as the source of a valid roleSearchId, which is real semantic value the schema lacks. It adds nothing about orgId, but that parameter is already handled in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 — 'Start a new run of a Search' — and immediately qualifies it with the intent ('find more people now, instead of waiting for its schedule'), which distinguishes it from the scheduling/creation siblings. It also tells the agent where the roleSearchId originates (listRoleSearches), so the tool can be identified without opening any schema.

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?

It states the triggering condition (want more people now rather than at the next scheduled run) and a hard prerequisite (confirm with the user first because each run consumes search credits), and it names the follow-up tool for reading results (getRoleSearch). What's missing is an explicit negative case — e.g., not to use this when a run is already in flight for the purpose of forcing a second run — but the guidance is well above implied.

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