Skip to main content
Glama

LEVA building cost estimates

The newest public LEVA project of a user

get_latest_project
Read-onlyIdempotent

The newest public project a LEVA user shared (not a LEVA reference design): product, author, place, size and the budget (total, materials, execution, hours; USD estimates, not quotes), with its link.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond them — that budgets are USD estimates rather than quotes, and that LEVA reference designs are excluded from the result — but says nothing about behavior when the user has no public projects.

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 defines the resource first and then enumerates the payload. The nested parenthetical field list is dense but every element adds information about the return value.

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?

With no output schema, the description correctly carries the burden of describing returned fields and does so thoroughly. It is still incomplete on two points an agent needs: which user's project is fetched, and whether a user with no public projects yields an empty result or an error.

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 and schema coverage is 100%, so the baseline applies. The only semantic gap is that the description does not state whose project is returned, which is exactly the kind of implicit assumption a no-parameter tool should spell out.

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?

Names a specific verb+resource ("The newest public project a LEVA user shared") and explicitly excludes a near-miss category ("not a LEVA reference design"), which helps distinguish it from get_project. However, it never says whose project — presumably the authenticated caller — leaving an ambiguity an agent must guess at.

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?

No when-to-use or when-not-to-use guidance relative to siblings such as get_project or get_project_prices. The reference-design exclusion is a scope constraint on the result set, not routing guidance between tools.

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