Skip to main content
Glama
Sign In
EasySourceFlow

EasySourceFlow

by john-ops-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

easysourceflow_search_outputs

Read-onlyIdempotent

Full-text search across generated Markdown outputs and retrieve links to the corresponding stored files.

Instructions

Full-text search generated Markdown outputs and return links to the stored Markdown files.

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

Input Schema

NameRequiredDescriptionDefault
qYesSearch query.
limitNo
sourceNoOptional source type filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so description does not need to repeat safety traits. Description adds basic function but no extra behavioral details (e.g., no mention of result limits or search behavior).

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?

Single sentence, 13 words, front-loaded and efficient. Every word adds value with no redundancy.

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?

Adequate for a simple search tool, but lacks details on search scope, matching algorithm, result format, pagination, or how links are structured. With no output schema, more context would help agent usability.

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 coverage is 67% (missing description for 'limit'), and the description adds no parameter-level details beyond the schema. It does not compensate for the missing parameter description or clarify 'source' filter.

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?

Description clearly states the tool searches generated Markdown outputs and returns links, with a specific verb and resource. Distinguishes from siblings as the only search-focused tool for Markdown outputs.

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?

Implies usage for searching Markdown outputs but provides no explicit guidance on when to use versus alternative tools or when not to use. Context is minimal.

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