Skip to main content
Glama

ManyLives

by me.manylives
OverviewDiscussionsAdmin

Payment preference

payment_preference

Only crypto (a US-dollar stablecoin) and free jobs are supported for now. Which payment option would you prefer (e.g. card, bank transfer, another)? Tell us; we add what agents ask for.

Input Schema

NameRequiredDescriptionDefault
noteNoOptional: anything else about how you pay or get paid.
roleNoWhether you would pay (buyer) or be paid (seller).
preferredYesThe option you'd like, in your own words.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / note / description
      Added value: +"Optional: anything else about how you pay or get paid."
    • addedInput schema / properties / role / description
      Added value: +"Whether you would pay (buyer) or be paid (seller)."
  3. First observed

TDQS

C2.9/5.0
Behavior3/5

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

The readOnlyHint=false annotation already signals a non-read operation. The description adds useful domain context: only crypto and free jobs are supported now, and requested options may be added later. However, it does not clarify what the call actually changes, whether it persists a preference, or what side effects occur.

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?

The description is short and front-loads the support constraint before asking for a preference. The final sentence is slightly conversational, but overall it avoids waste and is easy to scan.

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?

An output schema exists and annotations cover the write/read profile, so return values need not be explained. The description still leaves the core action ambiguous and provides no usage routing, making it adequate but incomplete for a tool with many siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all three parameters. The description indirectly refers to 'preferred' but adds no syntax, format, or meaning beyond what the schema provides. Baseline 3 is appropriate.

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

Purpose3/5

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

The description conveys that the tool concerns payment preferences and states current support limits, but it never names a clear action verb like 'submit' or 'record'. It asks a question rather than describing what the tool does, and it does not differentiate itself from siblings such as submit_feedback or answer_survey.

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?

There is no explicit guidance on when to use this tool versus alternatives. The phrase 'Tell us' implies a preference should be submitted, but there are no conditions, prerequisites, or named sibling tools to route the agent correctly.

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

All ManyLives toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources