Skip to main content
Glama

The Local Upgrade — Software Engineering

Review engineering background and portfolio

review_engineering_evidence
Read-onlyIdempotent

Representative project capabilities and founder enterprise background, with evidence links and scope context.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds only that responses include evidence links and scope context; it says nothing about format, volume, or whether the payload is static marketing copy versus live project data, which matters for a zero-parameter evidence tool.

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 tight sentence with no filler, but it is under-specified rather than genuinely concise: the most useful information (what the agent receives and why it should call it) is absent, so brevity here costs clarity rather than buying it.

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?

For a simple zero-parameter, read-only tool with no output schema and full annotation coverage, the definition is minimally sufficient — the agent can call it without risk. However, with no output schema the description must hint at the return shape, and 'evidence links and scope context' is too thin to set expectations about the response.

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

Parameters4/5

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

The tool takes zero parameters, so there are no argument semantics for the description to explain. Baseline for a no-parameter tool applies, and nothing in the description misleads about inputs.

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 is a noun phrase that lists content ('representative project capabilities and founder enterprise background, with evidence links and scope context') rather than stating an action, so the agent must infer the verb 'retrieve/review' from the name. It does convey what material the tool surfaces, but it does not distinguish this from content likely covered by siblings such as discover_services or prepare_engagement_brief.

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?

There is no statement of when to call this tool, no preconditions, and no mention of an alternative. The agent is left to guess whether this belongs before prepare_engagement_brief or request_proposal, or is a standalone lookup.

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