Skip to main content
Glama

Quote a human service (free)

quote_human_service
Read-only

What a human service order would cost, free. It answers our count ("70 words, English to Turkish", "40 lines of code"), price_cents, the promise, daily_limit (whether it fits what is left of your owner's limit today, or needs their approval by email) and quote_jws, a signed quote valid 24 hours. Send the whole brief, or text (per-word services, or a code review's code) or item_count (labels). Any other item takes item alone and gets its price for your owner (the first blueprint quotes 0); the email check takes item_count, the number of different entries in your list. Nothing is taken, and the brief is not kept (for an agent with an owner, only a keyed note of each address name we looked up, used for 5 minutes and deleted by our daily cleanup). The order counts the same way again: after your human's clear yes, pass max_price_cents to buy.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "item": "human-proofreading",
      "text": "This is a short example text.",
      "language": "en"
    },
    "name": "quote_human_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesA human service slug (search_catalog with shelf human).
textNoPer-word services: exactly the text you will order.
briefNoThe whole brief, exactly as you will order it.
languageNoProofreading quoted by text: the text's language, a tag such as en (our team's languages only).
item_countNoLabels: how many items. The email check: how many different entries your list has.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.
source_languageNoTranslation quoted by text: the text's language, a tag such as en (our team's languages only).
target_languageNoTranslation quoted by text: the language to translate into, a tag such as tr (our team's languages only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "item": "human-proofreading",
      +    "language": "en",
      +    "text": "This is a short example text."
      +  }
      +]
    • addedInput schema / properties / language / description
      Added value: +"Proofreading quoted by text: the text's language, a tag such as en (our team's languages only)."
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
    • addedInput schema / properties / source_language / description
      Added value: +"Translation quoted by text: the text's language, a tag such as en (our team's languages only)."
    • addedInput schema / properties / target_language / description
      Added value: +"Translation quoted by text: the language to translate into, a tag such as tr (our team's languages only)."
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Changed1 schema field changed
    • changedInput schema / properties / item_count / description
      Previous value: -"Labels: how many items."New value: +"Labels: how many items. The email check: how many different entries your list has."
  4. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, yet the description still adds real value: nothing is taken, the brief is not retained, only a keyed note of looked-up address names persists for 5 minutes pending daily cleanup, and the returned quote_jws is valid 24 hours. It also flags an edge case (the first blueprint quotes 0) that an agent would otherwise misread as an error. The privacy note's phrasing ('a keyed note of each address name we looked up') is vague enough to leave some doubt about what is retained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence front-loads the purpose well and almost every clause carries information, but the body is a dense run of parentheticals and overloaded pronouns ('It answers our count', 'Any other item takes item alone') that costs more parsing effort than the content warrants. Information density is high; readability is not.

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 8 parameters, a nested brief object, and no output schema, the description does the work of explaining return fields (count, price, promise, daily_limit, quote_jws) and the limit/approval consequence. It covers privacy and quote expiry, which an agent needs before sending a brief. Gaps are minor: it doesn't describe the failure shape when the daily limit is exceeded or when a slug is invalid.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes further by explaining which parameters pair with which item categories and that item_count has two different meanings depending on context (label count vs. number of distinct entries for the email check). It also implies text must be the exact text to be ordered. It says nothing about passport_token's role or the language-tag constraint beyond 'our team's languages only', leaving some schema-adjacent nuance to the schema itself.

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 action on a specific resource: prices out what a human service order would cost, for free, and enumerates what comes back (count, price_cents, promise, daily_limit, quote_jws). It is distinguishable from siblings like `buy` because it explicitly frames itself as the pre-purchase step. The telegraphic phrasing ('It answers our count') makes it slightly harder to parse than it needs to be, keeping it off a 5.

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 concrete per-service-type routing ('Send the whole brief, or text (per-word services, or a code review's code) or item_count (labels)') and states the follow-up path: after the human's clear yes, pass max_price_cents to buy. It lacks explicit 'do not use this when' exclusions and never names the sibling tools by name for lookup/approval paths, but the when-to-use context is clear.

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.