Skip to main content
Glama

Little Works

vocalize_work

Help a person name what they do — skills / work statement on Discover so others can hire and match proof.

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": {
      "who": "<who>",
      "does": "<does>"
    },
    "name": "vocalize_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
whoYesPerson or shop name
doesYesWhat they do — plain language
notesNo
placeNo
apiKeyNoRequired when LITTLEWORKS_MCP_API_KEY is set on the server

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely drops it. It never says whether this creates or overwrites a public Discover profile entry, whether the statement is visible publicly, whether repeated calls are idempotent, or that an API key may be required — that last point appears only in the schema, not the description.

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?

It is a single compact sentence with the audience/benefit front-loaded, so there is no padding. But the compression costs clarity — 'vocalize' and 'match proof' are non-obvious phrasing that an agent must interpret.

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

Completeness2/5

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

For a 5-parameter, two-required tool that appears to publish publicly visible work data with no annotations and no output schema, the single sentence is not enough. An agent knows roughly the intent but not the side effects, required identity, or return behavior, so it cannot call this confidently.

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

Parameters2/5

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

Schema coverage is 60%: who, does, and apiKey are documented in the schema, while notes and place are undocumented anywhere. The description contributes no parameter meaning at all — it doesn't explain what 'who' accepts (person vs shop), what 'place' controls, or what 'notes' is for.

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 the gist — producing a skills/work statement published on Discover — and hints at the downstream benefit ('so others can hire and match proof'). But the verb is fuzzy ('Help a person name what they do') rather than stating an operation like 'create or update a work statement', and it never distinguishes this from siblings such as list_work_experience or get_person_proof.

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 a stated motivation for using it (so others can hire and match proof), which implies the scenario. However, there is no explicit when-to-use, no prerequisites, no mention that a person must already exist, and no routing to alternatives for merely reading or listing work experience.

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