Skip to main content
Glama
Sign In
jaicp-mcp

jaicp-mcp

by CryLeech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

jaicp_specs

Provides the official JAICP/OpenAPI specifications for interacting with JAICP APIs. Use these specs to understand available endpoints, operations, and data models for building integrations with JAICP services.

Instructions

Official JAICP/Tovie OpenAPI specs this MCP was built from. No network.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It explicitly states 'No network,' which is a useful trait indicating local operation. However, it does not describe the output format, size, or any other behavior, so transparency is partial.

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?

The description is a single sentence that delivers the essential information—what the tool is and that it is local—without any filler. It is front-loaded and efficiently communicates the core purpose.

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?

Given the tool has no parameters, no output schema, and a simple purpose, the description covers the key facts. It states the tool's source and offline nature, which is sufficient for an agent to decide whether to call it. It could mention that it returns the full OpenAPI spec, but that is implied by the description.

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 has zero parameters, so the baseline for this dimension is 4. The description adds no parameter-specific information (there are none), but it does clarify that the tool returns specs, which aligns with the empty schema.

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 (the OpenAPI specs) and its provenance (built from), making the purpose clear. It does not explicitly contrast with sibling tools, but the name and description make it obvious this is about specs rather than calls or operations.

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?

No guidance is given on when to use this tool versus jaicp_call or jaicp_operations. The description does not mention use cases, prerequisites, or alternatives, leaving the agent to infer applicability.

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

Deploy Server

Other Tools