API Tool Calls

APA Citation Generator

apa_citation_generator

Read-onlyIdempotent

Format an APA reference and in-text citations from entered source metadata.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "2020",
      "type": "book",
      "title": "The Example Book",
      "authors": [
        {
          "given": "Jane",
          "family": "Smith"
        }
      ],
      "publisher": "Example Press"
    },
    "name": "apa_citation_generator"
  }
}

Input Schema

Name	Required	Description	Default
`doi`	No
`url`	No
`date`	No
`type`	Yes
`issue`	No
`pages`	No
`title`	Yes
`volume`	No
`authors`	No
`edition`	No
`editors`	No
`journal`	No
`changing`	No
`platform`	No
`siteName`	No
`bookTitle`	No
`publisher`	No
`retrieved`	No
`reportNumber`	No
`sentenceCase`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 4, 2026

TDQS

C2.9/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 and determinism profile is fully covered by structured data. The description adds only a light clarification that input is 'source metadata' rather than free text, and says nothing about formatting rules, error behavior on incomplete metadata, or validation. With annotations doing the heavy lifting, a 3 is appropriate.

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 front-loaded sentence with no filler; every word earns its place and the core action is stated first. It is arguably too sparse for a 20-parameter tool, but that is a completeness issue rather than wasted text.

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?

With 20 parameters, 0% schema description coverage, and no output explanation needed (an output schema exists), the description leaves the agent without any field-level or behavioral guidance. It does not clarify which fields apply to which source type or how partial metadata is handled, which is the critical missing context here.

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

Parameters2/5

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

Schema description coverage is 0% across 20 parameters, so the description must compensate and does not: it never mentions any field, the type enum (journal/book/chapter/webpage/report/video), or the meaning of flags like 'changing' and 'sentenceCase' (default true). 'Entered source metadata' is only a vague gesture at the field set. This is a substantial gap for a tool with 20 inputs.

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?

States a specific verb (format) and a specific resource (APA reference and in-text citations) plus the input domain (entered source metadata). An agent can immediately tell what this does, and no sibling tool overlaps with citation formatting, so differentiation is inherent rather than stated. It stops short of specifying scope (e.g., APA 7th edition, which citation styles for which source types).

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 guidance, no prerequisites, and no mention of alternatives or when this tool is inappropriate (e.g., for non-APA styles). The only implied usage is the one-sentence purpose itself. Nothing tells the agent what metadata is mandatory versus optional before calling.

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

All API Tool Calls tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?