Skip to main content
Glama

insc.one — INSC.1 Citation Layer

format_citation

Return a ready-to-paste citation string that leads with the INSC neutral citation, with optional parallel reporters and a registry-style footnote.

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": {
      "citation": "<citation>"
    },
    "name": "format_citation"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNoinsc_primary
citationYesINSC neutral citation or any resolvable reference.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full load. It correctly signals a non-destructive formatting operation and discloses the output structure (neutral citation first, optional parallel reporters, registry-style footnote), which is meaningful given there is no output schema. It does not say what happens when the reference is unresolvable, whether errors are thrown or a placeholder is returned, or whether the tool does any network lookup.

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?

One dense sentence with no filler, and the most important fact (the output leads with the INSC neutral citation) is front-loaded after the verb. Nothing is redundant, though the trailing clause stacks three output attributes that could be split for scannability.

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 two-parameter, no-annotation, no-output-schema tool, the description covers what the artifact looks like but leaves the style enum and failure behavior undocumented. Given the formatting tool's simplicity that is acceptable, but the enum gap is the notable shortfall.

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 coverage is 50%: 'citation' is documented in the schema, but the 'style' enum (insc_primary/insc_only/full_parallel) is not explained anywhere. The description's mention of 'optional parallel reporters and a registry-style footnote' hints at what the styles toggle but never maps them to the enum values, so the agent must guess which style yields which of the advertised components.

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 verb 'Return' plus the resource 'ready-to-paste citation string' makes the operation concrete, and 'leads with the INSC neutral citation' pins down the output shape. It stops short of naming a sibling such as resolve_citation, so an agent must infer that this formats rather than resolves. Still clearly distinct from audit/check tools by the citation-string framing.

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 only implied: the words 'ready-to-paste' suggest a downstream copy/paste or brief-drafting context, but there is no explicit when-to-use statement, no prerequisite (e.g. citation must already resolve), and no stated alternative for raw resolution.

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