Skip to main content
Glama
Sign In
Testimonial.to MCP Server

Testimonial.to MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Verify the selected Space key

verify_space
Read-onlyIdempotent

Verify access to a private Testimonial.to Space with a configured account key, returning the Space ID and account email as private metadata.

Instructions

Explicit native key verification. Response includes Space id and account email; private metadata, not ownership or all-action proof.

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": "verify_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoExact configured private account profile label; not a tenant or provider account ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuine value by disclosing what the response contains (Space id, account email) and bounding what verification proves — private metadata, not ownership. It stops short of describing auth requirements or failure behavior.

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 compact sentences that lead with the action and follow with response/scope caveats. It is front-loaded and free of filler, though the second sentence's phrasing is dense and slightly cryptic.

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?

No output schema exists, and the description partially compensates by naming the returned fields. But for a verification tool it omits the key questions — what result indicates a valid vs invalid key, and whether errors are surfaced — leaving the definition only adequately complete.

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 single optional 'account' parameter is fully documented in the schema itself. The description adds no parameter-level detail, which is the expected baseline when the schema carries the load.

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 title 'Verify the selected Space key' and the phrase 'Explicit native key verification' convey the resource (a Space API key) and action (verification), and the description notes the response returns Space id and account email. However, the wording is elliptic ('native', 'explicit') and never plainly states it checks whether the configured key is valid, so an agent must infer the core purpose.

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 guidance on when to call this versus alternatives, nor any prerequisite or trigger context. The only scoping is a negative: 'not ownership or all-action proof,' which limits expectations but does not tell the agent when verification is warranted.

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

Deploy Server

Other Tools