Skip to main content
Glama
Sign In

EXZA Remote

by de.exza.remote
OverviewDiscussionsAdmin

Get commander search results

exza_get_commander_search_results
Read-onlyIdempotent

Fetch one page of results for a prior exza_start_commander_search ID. Does not start a new search; offset and limit control pagination. Requires account-bound computer:write OAuth and any prompted local owner approval.

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

Input Schema

NameRequiredDescriptionDefault
idYesIdentifier returned by the corresponding start/list operation; not a device PIN.
limitNoPage length, subject to server-side maximum.
offsetNoPagination or output cursor offset; use returned continuation data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered structurally. The description adds genuinely useful context the annotations cannot convey: account-bound computer:write OAuth plus possible prompted local owner approval, and that offset/limit govern pagination. It stops short of describing the shape of a results page or how continuation data is surfaced.

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?

Three short sentences, front-loaded with purpose and immediately followed by the negative scoping statement and the auth prerequisite. No filler and nothing buried.

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

Completeness4/5

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

For a read-only paginated fetch with full schema coverage and no output schema, the description covers purpose, prerequisite state, pagination control, and auth requirements. The main remaining gap is return-value expectations (page shape, continuation data), which the description leaves to the schema.

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 description coverage is 100%, so id, limit and offset are already documented, including the 'not a device PIN' caveat. The description only restates that offset and limit control pagination, adding no syntax, defaults, or maximums beyond the schema. Baseline 3 applies.

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 specific verb and resource ('Fetch one page of results') scoped to a prior exza_start_commander_search ID, and explicitly negates the sibling action ('Does not start a new search'). An agent can distinguish this from exza_start_commander_search and exza_list_commander_searches without opening the 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?

Clear context: use after a prior start operation, with an explicit exclusion that this does not initiate a search. It does not name exza_list_commander_searches as the way to discover existing IDs, so the routing guidance is clear but not complete.

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

All EXZA Remote toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources