Skip to main content
Glama

The Marketing Vault

Add proof (testimonials and results)

add_proof

Saves testimonials, client results or company figures to a business as verified proof that Vault generations may quote. Does not use a generation.

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": {
      "items": "<items>"
    },
    "name": "add_proof"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
business_profile_idNoBusiness id from list_businesses. Defaults to the default Business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), so the bar is lower. The description adds two pieces of genuinely useful context beyond them: the write persists data for later quoting in generations, and it consumes no generation credit. It stays silent on duplicate handling, even though idempotentHint=false implies re-submission may create duplicates.

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

Conciseness5/5

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

Two tight sentences: the action and payload first, then the purpose, then the cost caveat last. Nothing is repeated from the title and no sentence can be removed without losing information.

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?

For a non-destructive, non-idempotent write with no output schema, the definition covers what gets stored, why it matters, and that it costs no generation. The remaining gap is the return value and duplicate/overwrite behavior, which is a modest omission rather than a blocking one.

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 50% by the top-level count, but the nested item fields (kind, quote, metric, context, source_url, author_*) are each documented in the schema. The description only loosely maps its three phrases to the enum values testimonial/case_study/stat and adds nothing about batching up to 25 items or how business_profile_id defaults.

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?

The description opens with a concrete verb and resource — 'Saves testimonials, client results or company figures to a business' — and narrows the payload types to the same three kinds the schema accepts. It also states the downstream purpose ('verified proof that Vault generations may quote'), so an agent understands both the action and the artifact it produces.

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?

'Does not use a generation' gives implicit routing value by signalling this is a cheap, non-generation write, which helps separate it from the write_* family. However, there is no explicit when-to-use guidance, no exclusions, and no mention of when to prefer save_reference_note or save_output for similar freeform text.

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