Skip to main content
Glama

LEVA building cost estimates

One public LEVA project

get_project
Read-onlyIdempotent

One public LEVA project by the id from its link (?p=): a LEVA reference design or a budget its author made public -- plan size, rooms, roof, place, and the budget (total, materials, execution, hours; USD estimates, not quotes).

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": {
      "id": "<id>"
    },
    "name": "get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe ?p= id of a project link, 6-12 lowercase letters / digits

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: results are limited to public projects, and the money figures are USD estimates, not quotes — but it says nothing about failure behavior when the id is private or unknown.

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 front-loaded sentence that leads with the identity and scope, then enumerates payload fields. It is dense with em-dashes and parentheticals but no sentence is wasted.

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, so the description must describe the return, and it does: plan size, rooms, roof, place, and budget breakdown with a caveat on estimate vs quote. Only the error/not-found path is left unstated for a one-parameter lookup tool.

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 100% and already documents the id as 'the ?p= id of a project link, 6-12 lowercase letters / digits'. The description's 'by the id from its link (?p=<id>)' restates that without adding format or validation detail, so the 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?

States a specific verb+resource ('One public LEVA project by the id from its link') and scopes it to public projects, spelling out the two content types (reference design or self-published budget). It implicitly separates itself from get_latest_project by requiring an explicit ?p= id, though it never names that sibling.

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?

Usage is only implied: you must have a ?p= project link id, and the tool returns public projects only. There is no explicit when-to-use vs when-not guidance and no pointer to get_latest_project or get_project_prices for related lookups.

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