Skip to main content
Glama

Inspect selected project excerpts

merron_scan_project
Read-onlyIdempotent

Find possible AI integrations, model calls, disclosure wording and sensitive-use wording in user-selected project excerpts. Returns file/line references and follow-up questions, not a legal classification. First explain that the excerpts will be sent to Merron and obtain the user's agreement. Never send secrets, personal customer records, whole repositories or files the user has not authorised. Does not fetch URLs, execute code, persist inputs or access private cases.

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": {
      "sharingConfirmed": "<sharingConfirmed>",
      "files": "<files>"
    },
    "name": "merron_scan_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYes
sharingConfirmedYesTrue only after the user agrees to send these selected excerpts to Merron.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations: annotations already say readOnly/idempotent/non-destructive, and the description adds that it does not fetch URLs, execute code, persist inputs, or access private cases, plus that outputs are references and questions rather than a verdict. That is exactly the extra context the safety hints cannot convey.

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?

Five short sentences, each carrying distinct information: what it finds, what it returns, the consent gate, the prohibitions, and the non-capabilities. Front-loaded with the purpose before any constraints.

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?

No output schema exists, yet the description explains the shape of the result (file/line references and follow-up questions), and it covers the consent gate and data-handling limits. Minor gaps remain around the input batching limits and what an empty or low-confidence result means.

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 50% — sharingConfirmed is documented in-schema, while the files objects (path, text, startLine) are not described there. The description partially compensates by framing inputs as 'user-selected project excerpts' that must be authorised and must not be whole repositories, but it never explains the per-file path/text/startLine fields.

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 concrete verb and target: find AI integrations, model calls, disclosure and sensitive-use wording in user-selected excerpts. It implicitly separates itself from siblings by declaring 'not a legal classification' (contrasting with merron_screen_ai_act), but never names an alternative explicitly.

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?

Gives a clear precondition flow (explain the excerpts go to Merron, obtain agreement) and explicit exclusions (secrets, personal customer records, whole repositories, unauthorised files). It stops short of naming which sibling to use for a legal classification or follow-up questions.

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.

Resources