Skip to main content
Glama

EarlyLore

earlylore_get_evaluation

Read-onlyIdempotent

Read the complete structured blueprint of an evaluation report (5-dimension ratings, Core Bet, Consensus Trap, 2 strategy routes, 4-week MVP blueprint, 8-seat orthogonal expert & buyer roundtable, and direct competitors). Pass an evaluationId, or omit it to read the latest completed report.

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

Input Schema

NameRequiredDescriptionDefault
queryNoSearch your past evaluation reports by idea keyword
evaluationIdNoEvaluation report UUID (omit to return the latest completed report for the current account)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's real addition is the payload shape (5-dimension ratings, Core Bet, Consensus Trap, routes, MVP blueprint, roundtable, competitors) and the default-to-latest behavior — that is useful context beyond the annotations, but nothing about error behavior, empty states, or size/pagination is disclosed.

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?

Two sentences, front-loaded with the resource and its contents, then the invocation rule. The parenthetical enumeration is dense but every item tells the agent what it can rely on receiving; no filler.

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?

With no output schema, the description carries the burden of describing the return payload, and it does so concretely. The one gap is the undocumented 'query' search pathway in prose, which is left entirely to the schema for a tool that otherwise explains both invocation modes.

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 description coverage is 100% and both parameters are documented in-schema. The description restates the evaluationId omission behavior the schema already states and says nothing at all about the 'query' keyword parameter, so it adds no meaning beyond structured fields. Baseline 3 applies.

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 opens with a specific verb ('Read') and resource ('complete structured blueprint of an evaluation report'), then enumerates the report's contents so the agent knows exactly what artifact it gets. The resource is clearly distinct from sibling tools like get_design_dna or get_market_pulse, though it never explicitly contrasts itself with them.

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 gives conditional invocation guidance for the ID case ('Pass an evaluationId, or omit it to read the latest completed report'), which is genuinely useful. However, there is no guidance on when to choose this tool over the other earlylore_get_* siblings, so the when-to-use decision is only implied.

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.