Skip to main content
Glama

Ergini: hire an AI engineer

List services and price ranges

list_services
Read-onlyIdempotent

List the five services Ergin offers (AI agent development, AI integration, AI workflow automation, MVP development, embedded engineer), each with a one-line description, its page and its published price range and tiers, plus the hourly option and the free discovery call. Use it when the user asks what Ergin does or what his work costs in general.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 handled structurally. The description adds real value by disclosing the shape of the payload (one-line description, page, price range and tiers, hourly option, free discovery call), but since no output schema exists it could have been more precise about return format. Adequate beyond annotations, not rich.

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?

Two sentences, front-loaded with the verb and the payload contents, followed immediately by the usage trigger; nothing is redundant with the title. The parenthetical list of five services is long but each item materially helps the agent match a user's question, so it broadly earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, read-only catalog tool with no output schema, the description covers what is returned, at what granularity (one-line descriptions, page, price ranges, tiers), and when to call it. Nothing an agent needs in order to invoke it correctly is missing.

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, so there is no parameter meaning to convey and the baseline of 4 applies. The description correctly implies a parameterless, catalog-style call without inventing arguments.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("List") plus the exact resource and enumerates the five concrete items returned (AI agent development, AI integration, AI workflow automation, MVP development, embedded engineer), along with page, price range, tiers, hourly option, and discovery call. An agent can distinguish this from estimate_project or list_case_studies without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger: "when the user asks what Ergin does or what his work costs in general." The phrase "in general" implicitly points away from a specific-quote tool such as estimate_project, but no sibling is named as an alternative, so the routing is clear rather than fully explicit.

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