Skip to main content
Glama

Smarty Pants

How to start

get_started
Read-onlyIdempotent

How to start using Smarty Pants: sign-up link, free starter credit, the OpenAI-compatible API base URL and a ready-to-run example. No sign-in needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds one genuinely useful behavioral fact — no sign-in is required — plus the specific payload contents, but says nothing about response format or whether the content is static versus refreshed.

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?

A single sentence, front-loaded with the purpose and then a compact list of what is returned, with the authentication caveat last. No filler or repetition; every clause carries 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?

There is no output schema, so the description carries the burden of describing the return value, and it does so by enumerating the four payload elements. For a simple, zero-parameter onboarding lookup this is close to sufficient, with only the response format left unspecified.

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, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The enumerated content list gives the agent a reasonable expectation of what a call yields without adding any misleading parameter hints.

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 states a specific resource ('How to start using Smarty Pants') and enumerates its contents: sign-up link, free starter credit, OpenAI-compatible API base URL, and a ready-to-run example. An agent can tell this is an onboarding/documentation lookup, distinct from the sibling tools about models and cost estimates, though it never uses a verb like 'returns' or 'retrieves'.

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?

Usage is implied by 'How to start' — an agent can infer this is for setup/onboarding questions — and 'No sign-in needed' signals it is available before authentication. However, there is no explicit when-to-use or when-not-to-use guidance and no routing to siblings such as estimate_cost or list_models once onboarding is done.

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