Skip to main content
Glama
Sign In
Search Evidence

Search Evidence

by baeseokjae
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_status

Read-onlyIdempotent

Check local tool availability and optionally verify account or property access before running search evidence queries.

Instructions

Show local availability and optionally check account/property access.

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

Input Schema

NameRequiredDescriptionDefault
remoteNo

Output Schema

NameRequiredDescriptionDefault
okNo
dataNo
errorNo
warningsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so safety is covered. The description adds a useful cue that the remote branch touches account/property authorization (consistent with openWorldHint), but it doesn't say what happens on auth failure, what 'local availability' checks, or whether the remote check has side effects like token refresh.

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?

One short sentence, front-loaded with the primary behavior and the optional extension. It wastes no words, though brevity here comes partly from under-specification rather than tight editing.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, but the description still leaves the core question unanswered: what 'availability' means, what an account/property access check returns or requires, and how the remote flag changes behavior. For a tool with an undocumented parameter and a vague resource, this is not enough.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single 'remote' boolean, and the description never names or defines that parameter — 'optionally check account/property access' only obliquely implies remote=true. The agent must guess that the optional behavior maps to the boolean flag.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ('Show') and two loosely defined resources ('local availability' and 'account/property access'), but never says what is being checked for status or what domain (e.g., Search Console properties) this applies to. An agent can guess it's a read-only diagnostic but cannot distinguish it clearly from siblings like search_verify_live or search_inspect_urls.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Optionally check' hints that the remote check is opt-in, but there is no statement of when to call this versus any of the nine sibling search_* tools, and no preconditions or exclusions. The agent is left to infer usage entirely.

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