Skip to main content
Glama

About MotifyMe

about_motifyme
Read-onlyIdempotent

Who MotifyMe is, what it offers and the main public urls.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety and determinism profile is fully covered. The description adds only that the payload is company identity, offering summary, and public URLs, which is modest content-scope context; it says nothing about payload size or shape.

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?

A single short sentence with no filler and the core content categories front-loaded. It is a fragment rather than a complete clause, but nothing in it is wasted.

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?

For a zero-parameter, annotation-covered read tool this is close to sufficient, and the description does sketch the returned content. With no output schema, however, an agent still cannot know whether to expect a narrative blurb, a link list, or structured fields, so it is only adequate.

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

Parameters4/5

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

The tool takes zero parameters, which is the baseline-4 case, and the description correctly implies a parameterless call by framing the result as a fixed body of information. Nothing about arguments needs explaining because there are none.

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

Purpose4/5

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

The description names a concrete resource ('Who MotifyMe is, what it offers') plus a concrete return category ('main public urls'), so an agent can tell this is a static company/about-info lookup rather than a vehicle-data query like its siblings. It lacks an explicit verb and never contrasts itself with get_site_page or list_site_pages, which is the only thing keeping it from a 5.

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 when-to-use or when-not-to-use guidance at all. The definition does not say whether this is the entry point for site orientation or how it differs from the site-page readers in the sibling set, leaving the agent to infer usage from the phrase 'about'.

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