Skip to main content
Glama

Ergini: hire an AI engineer

Estimate a project

estimate_project
Read-onlyIdempotent

Given a free-text project description, say which of Ergin's services fits, its published price range, the tier a build like it usually lands in and the closest use cases. This is a published range, never a quote: the real price comes in writing after a free 30-minute call. Matching is keyword-based, so a description that names the problem, the systems and the volume matches best.

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": {
      "description": "<description>"
    },
    "name": "estimate_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
descriptionYesWhat should be built, in plain words: the problem, the systems involved, rough volumes. Leave out names, emails and other personal or confidential details.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish this is a safe, idempotent, closed-world read, so the description is free to add the things that matter instead: results are keyword-based rather than semantic, and prices are published ranges rather than quotes. That expectation-setting is exactly the kind of context an agent cannot derive from the schema.

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?

Three sentences, front-loaded with the output contract before the disclaimer and then the input guidance. Dense with no filler, though the phrasing around 'the tier a build like it usually lands in' is slightly loose for a structural summary sentence.

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?

There is no output schema, and the description compensates by enumerating the four returned elements, which is adequate. It stops short of describing result shape or what happens when nothing matches, leaving a moderate gap for a tool whose entire value is its return payload.

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?

With one parameter at 100% schema coverage, the schema already defines length and content, but the description adds real signal by saying the problem, systems, and rough volume are what drive match quality. It reinforces the privacy note already in the schema without contradicting it.

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 names a concrete transformation: from a free-text project description to a service match, published price range, typical tier, and closest use cases. That is specific enough that an agent knows exactly what comes back, though it never contrasts itself with siblings like find_use_cases or list_services, which return adjacent information.

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 usage boundaries by saying the real price comes 'in writing after a free 30-minute call', which points at book_call without naming it. The only explicit guidance is about how to phrase the input for good keyword matching, not when to pick this over the listed alternatives.

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