Skip to main content
Glama
Sign In
stream-estate

stream-estate

Official
by StreamEstate
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list-searches

List your saved real estate searches with options to filter by title or notification status. Retrieve and manage property search alerts in one view.

Instructions

List all saved searches for the authenticated user. Can filter by notification status and title.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list-searches"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number
titleNoFilter by title
orderByTitleNoSort by title
notificationEnabledNoFilter by notification status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It discloses that the operation is scoped to the authenticated user and supports filtering, but it does not specify behavior such as pagination defaults, whether the list is empty-safe, or if this is a read-only operation, though 'List' implies non-mutating.

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 concise sentence that immediately states the core function and provides useful filter context without extraneous words.

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 list operation with no annotations or output schema, the description gives the essential purpose but omits details about the return structure or pagination behavior, which the page parameter hints at but doesn't clarify.

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 coverage is 100%, so the baseline is 3. The description mentions filtering by notification status and title, echoing two parameters, but adds no extra semantic detail beyond the schema descriptions.

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 a specific verb 'List' and identifies the resource 'saved searches for the authenticated user' with the ability to filter, distinguishing it clearly from sibling tools like get-search or create-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 description clearly states this tool lists saved searches for the authenticated user, providing context on when it should be used. It does not explicitly exclude alternatives like get-search for individual searches, but the scope is clear enough.

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