Skip to main content
Glama
adrian-capraru-mcp

adrian-capraru-mcp

Services

list_services
Read-onlyIdempotent

Lists the consultant's published fixed-price project tiers and consultations, including delivery days and deliverables, to help users identify a suitable service.

Instructions

Published offers: 12 fixed-price projects (3 tiers each, with delivery days and what is included) and 3 consultations. Prices are quoted on his Upwork profile or after a discovery call.

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 observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety needs no restating. The description adds real value beyond them by disclosing the return content structure — project counts, three-tier packaging, delivery days, what is included — plus a boundary note that pricing is not included and lives elsewhere. It does not describe ordering or formatting, which is a minor residual gap.

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 tight sentences, front-loaded with the inventory of offers, then a short boundary note on pricing. Every clause earns its place; nothing is redundant with annotations or schema.

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 parameters and no output schema, the description must convey what comes back, and it does so concretely (counts, tier structure, inclusions). Safety and determinism are handled by annotations. An agent could call this correctly, though it would have to guess the relationship to how_to_hire and check_availability.

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 schema has zero parameters and 100% coverage, so there is nothing for the description to disambiguate. Baseline 4 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 names the resource precisely — 'Published offers' — and enumerates its shape (12 fixed-price projects with 3 tiers, delivery days, inclusions, plus 3 consultations), so an agent knows exactly what this returns. It stops short of an explicit verb or a direct contrast with siblings like how_to_hire or check_availability.

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: an agent must infer that this is the browse-the-catalog call while how_to_hire handles the hiring process and check_availability handles scheduling. The line about prices being on the Upwork profile or after a discovery call hints at where this tool's coverage ends, but no alternative sibling is named and no when-not condition is stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.