Skip to main content
Glama
Sign In
stream-estate

stream-estate

Official
by StreamEstate
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-search

Retrieve complete details of a specific saved search by its ID, including criteria and settings.

Instructions

Get details of a specific saved search by its ID.

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": {
      "id": "<id>"
    },
    "name": "get-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSearch ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says 'Get details,' which gives minimal insight into return format, possible error behavior, or permissions, and does not enumerate what 'details' are included.

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 a single, front-loaded sentence that states the action and resource with no redundant wording.

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

Completeness3/5

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

For a simple one-parameter get-by-ID tool, the description is minimally adequate but incomplete: it does not specify what fields the returned details include, nor behavior when the ID is not found. The tool's low complexity partially compensates for this gap.

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?

The schema already fully documents the single parameter with 100% coverage, describing 'id' as 'Search ID.' The description adds little beyond this, merely reinforcing that the ID identifies a specific saved search without providing format examples or additional nuance.

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 uses the specific verb 'Get' with the resource 'specific saved search' and identifies the selection mechanism by ID. This clearly distinguishes it from sibling tools like list-searches and delete-search.

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 phrase 'by its ID' establishes a clear context for when to use this tool: to retrieve one saved search when the ID is known. It implicitly contrasts with list-searches for listing all searches, though it does not explicitly name alternatives or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools