Skip to main content
Glama

Search collected data

writ_search_data
Read-onlyIdempotent

Searches everything the account's workflows already collected for a term, without running anything.

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": {
      "q": "<q>"
    },
    "name": "writ_search_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes
limitNo
deviceNo
workflowNo
workflow_idNo
preview_charsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / device
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / preview_chars
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / workflow
      Added value: +{
      +  "type": "string"
      +}
  2. Changed5 schema fields changed
    • removedInput schema / properties / device
      Removed value: -{
      -  "description": "A linked Writ desktop's agent_id (writ_devices) to act on. Omitted: the desktop this connection chose with writ_devices action='use', if any.",
      -  "type": "string"
      -}
    • removedInput schema / properties / limit / description
      Removed value: -"Rows per workflow (default 10)."
    • removedInput schema / properties / preview_chars
      Removed value: -{
      -  "description": "Cut matched string cells to this many characters (default 300; 0 = full cells).",
      -  "type": "integer"
      -}
    • removedInput schema / properties / q / description
      Removed value: -"Search term (required)."
    • removedInput schema / properties / workflow
      Removed value: -{
      -  "type": "string"
      -}
  3. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the meaningful behavioral point that the search touches only pre-existing collected data and triggers no collection run. It says nothing about result volume, truncation, or how limits are applied.

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?

A single front-loaded sentence with no filler, and the key scope constraint comes last for emphasis. Its brevity is efficient, though it borders on under-specification given the six parameters it must support.

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?

For a six-parameter search tool with no output schema and no parameter documentation anywhere, the description does not do enough: it omits what a result looks like, how filters combine, and what preview_chars or the workflow identifiers do. An agent could call it, but not confidently.

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% across six parameters, and the description only implies that 'q' is a search term. It never explains limit, device, workflow vs. workflow_id (why both?), or preview_chars, which is the most opaque parameter and likely controls returned text truncation. The description leaves nearly all parameter meaning unstated.

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

Purpose4/5

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

States a specific verb ('Searches') and a precisely scoped resource: data the account's workflows have already collected, matched on a term. The trailing clause 'without running anything' separates it from execution tools like writ_run_workflow or writ_run_saved_crawl, though no sibling is named directly.

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

Usage Guidelines3/5

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

'without running anything' implies the use case (querying already-collected data rather than triggering new collection), which is genuine implied guidance. However, there is no explicit statement of when to prefer this over writ_workflow_data, writ_saved_crawl_data, or writ_export_data, and no prerequisites or exclusions.

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.