Skip to main content
Glama

create_testimonial

Create a Testimonial record.

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": {
      "display_name": "<display_name>",
      "comment": "<comment>",
      "rating": "<rating>"
    },
    "name": "create_testimonial"
  }
}

Input Schema

NameRequiredDescriptionDefault
sportNoSport the review relates to (optional)
ratingYesStar rating from 1 to 5 (maximum: 5; minimum: 1)
statusNoApproval status set by an adminpending
commentYesReview text written by the user (maxLength: 400; minLength: 10)
featuredNoWhether an admin has featured this review on the home page
photo_urlNoOptional win screenshot uploaded by the user
reviewed_atNoWhen an admin approved or rejected the review (format: "date-time")
display_nameYesDisplay name shown on the review (maxLength: 30; minLength: 2)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / comment / description
      Previous value: -"Review text written by the user (minLength: 10; maxLength: 400)"New value: +"Review text written by the user (maxLength: 400; minLength: 10)"
    • changedInput schema / properties / display_name / description
      Previous value: -"Display name shown on the review (minLength: 2; maxLength: 30)"New value: +"Display name shown on the review (maxLength: 30; minLength: 2)"
    • changedInput schema / properties / rating / description
      Previous value: -"Star rating from 1 to 5 (minimum: 1; maximum: 5)"New value: +"Star rating from 1 to 5 (maximum: 5; minimum: 1)"
  2. First observed

TDQS

C2.5/5.0
Behavior2/5

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

The only annotation is destructiveHint=false, so the description carries the burden of disclosing behavior and does not. It does not mention that admin-only fields like status and featured are set, that defaults (pending, false) are applied, or what happens on validation failure for required fields.

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 single sentence is free of waste and front-loaded, but it is under-specified rather than genuinely concise. There is no structure to speak of because there is only one short clause.

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?

This is a mutation tool with 8 parameters, three of which are required, and it has only a minimal destructiveHint annotation and no output schema. The description says nothing about required fields, validation constraints, admin-only attributes, or the result of a successful creation.

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 every parameter is already documented in the schema, including enums, ranges, and defaults. The description adds no meaning beyond the schema, but the baseline of 3 applies when structured fields do the heavy lifting.

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 gives a verb and resource ("Create a Testimonial record"), so the basic action is identifiable. However, it is essentially a restatement of the tool name and adds no scope detail, such as who can create records or what the record represents, to distinguish it from update_testimonial or query_testimonial.

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 use this tool versus update_testimonial or query_testimonial, and no prerequisites or context are given. The name implies creation, but the description contributes nothing about alternatives or conditions.

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