invokit-mcp

Official

Overview Schema Source Related Servers Discussions Admin

get_manifest

Retrieve the invok.it platform manifest to discover available capabilities, API endpoints, authentication methods, and rate limits. Use it to understand platform features before building integrations.

Instructions

Get the invok.it platform manifest — capabilities, endpoints, auth methods, and rate limits.

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_manifest"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 30, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get' implies a read-only operation, and the enumerated contents signal what the response will cover, but the description does not explicitly state that this operation has no side effects or whether any auth is required to call it.

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, front-loaded sentence that uses an em-dash to efficiently enumerate the manifest's contents. Every word earns its place, and it is neither padded nor under-specified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool with an output schema present, the description is complete and useful. It tells the agent exactly what the manifest covers, and there are no missing invocation details or ambiguous side effects that would block correct use.

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 there are no parameter semantics to document. The input schema already reflects this completely, and the description adds no parameter-related confusion. Baseline 4 is appropriate for a no-parameter tool.

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

Purpose5/5

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

The description clearly states the verb 'Get' and the resource ('the invok.it platform manifest'), and enumerates its contents: capabilities, endpoints, auth methods, and rate limits. It is immediately distinguishable from sibling tools like get_app or get_tool, which target specific resources rather than the platform-wide manifest.

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?

The description implies this is the tool for retrieving platform-level metadata, but it does not explicitly state when to use it versus alternatives. Since it is the only manifest-related tool among the siblings, the intended use is reasonably inferable, but the guidance is not explicit.

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

Deploy Server