Skip to main content
Glama

Read a search

getRoleSearch
Read-onlyIdempotent

Read one Search (roleSearchId from listRoleSearches): its criteria and the last change Clera made to them, schedule, quality floor, last runs, a suggested bigger change when the yes and no calls point to one, and a page of the people it found, best fit first.

Each person has a 0-100 fit, a one-line reason, whether they fall below the Search's quality floor, the sources that found them, any yes or no already given and the best way in: a Clera intro, a teammate who knows them, or cold. Returns 10 people per call; when hasMore is true, call again with cursor set to nextCursor.

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": "getRoleSearch"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
peopleYes
searchYes
hasMoreYes
nextCursorYes

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?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, not open-world), and the description still adds substantially: page size of 10, the hasMore/nextCursor loop, ordering by best fit, and a disclosure that Clera privately records inputs and results for usage tracking. Those operational and privacy details are not derivable from the structured fields.

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?

Front-loaded with the tool's identity and identifier source, then the payload description, then the pagination rule — a sensible order. Some phrasing is denser than needed (the 'suggested bigger change when the yes and no calls point to one' clause), but nearly every sentence carries operational value.

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 read tool with an output schema already present, the description goes beyond the requirement by characterizing the returned people records, fit scoring, and inclusion signals. Combined with the pagination and privacy notes, nothing an agent needs to invoke 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 only 33% (only orgId is documented), but the description compensates for both bare parameters: roleSearchId is sourced from listRoleSearches and cursor is defined as the nextCursor value returned when hasMore is true. The only minor gap is that orgId's multi-org condition is left to 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?

States a precise verb+resource (read one Search) and immediately anchors the identifier by pointing at listRoleSearches, which distinguishes it from the list sibling. The description then enumerates the concrete contents (criteria, schedule, quality floor, runs, people found), so an agent knows exactly what it is fetching.

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?

The parenthetical '(roleSearchId from listRoleSearches)' plus the pagination instruction ('when hasMore is true, call again with cursor set to nextCursor') makes the call sequence explicit. It lacks an explicit when-not or a named alternative for looking at many searches in bulk, which keeps it short of a 5.

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