Skip to main content
Glama

AI Site Scorer

enhance_report

Run LLM deep analysis on a completed report. Returns detailed AI analysis with priority issues and actionable recommendations. Pricing: Included with Pro subscription, or $0.005 USDC per request via x402 (no account or free plan).

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": {
      "job_id": "<job_id>"
    },
    "name": "enhance_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe UUID job_id of a completed report.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses the LLM-analysis nature, the output type, the Pro/x402 pricing model, and that no free plan is available. It does not disclose side effects such as whether the analysis is persisted, whether repeated calls create duplicates, latency characteristics, or failure behavior for incomplete reports.

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?

The description is three sentences: action, return, and pricing. It is front-loaded with the core action and each sentence carries relevant information. The pricing sentence is necessary because it affects whether and how the agent can invoke the tool.

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 one-parameter tool with no output schema, the description adequately summarizes the return value and cost model. However, it omits side-effect and state-change behavior, and does not help the agent choose this tool over nearby siblings such as generate_fix_prompt or get_report, leaving meaningful gaps.

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?

There is only one parameter, and the schema description already covers it fully as 'The UUID job_id of a completed report.' The description reinforces the 'completed report' constraint but adds no new syntax, format, or validation detail beyond the schema. With 100% schema coverage, the baseline of 3 is appropriate.

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?

The description states a specific verb and resource: 'Run LLM deep analysis on a completed report.' It also names what is returned ('detailed AI analysis with priority issues and actionable recommendations'), so the agent can distinguish this from report retrieval or URL analysis siblings. It does not explicitly name the sibling alternatives, which keeps it below a 5.

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?

It implies the prerequisite that the report must be completed, which is useful context for when this tool is valid. However, it gives no explicit when-to-use versus get_report, generate_fix_prompt, list_recent_analyses, or other siblings, and no when-not-to-use guidance.

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