Skip to main content
Glama
Sign In

crosscheck

by com.crosscheckapi
OverviewDiscussionsAdmin

Look up a past skillcheck

skillcheck_lookup

Free. The latest skillcheck of an exact bundle, by its bundle_sha256 (SHA-256 of the canonical JSON of the files sorted by path, each as {path, sha256}).

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": {
      "bundle_sha256": "<bundle_sha256>"
    },
    "name": "skillcheck_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
bundle_sha256Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. It discloses that the operation is free and that it returns the 'latest' skillcheck for an 'exact' bundle, but it does not mention error handling (e.g., invalid hash, no matching bundle), response format, or any side effects. It omits critical behavioral context an agent would need for robust invocation.

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, information-dense sentence. It front-loads the cost ('Free') and then states the core purpose and the exact input requirement. Every word contributes value; there is no redundancy or fluff.

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 tool with a single parameter and no output schema, the description adequately explains the input and the general behavior, but it does not specify what the tool returns (e.g., the skillcheck object, a status, or an error message). It also lacks guidance on edge cases like nonexistent bundles. Given the lack of an output schema, the description should have clarified the return value to be fully complete.

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

Parameters5/5

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

The schema only provides a pattern for the parameter, but the description adds substantial meaning: it explains that bundle_sha256 is the SHA-256 of the canonical JSON of files sorted by path, each as {path, sha256}. This is a detailed semantic definition that goes far beyond the schema, giving the agent precise instructions on how to construct the input.

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 states a specific verb ('look up'), a resource ('latest skillcheck'), and a precise identifier ('bundle_sha256') with a detailed definition of that hash. It clearly distinguishes this tool as an exact-match lookup by hash, setting it apart from broader sibling tools like 'skillcheck' without needing explicit naming.

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 guidance on when to use this tool versus alternatives. It does not mention scenarios like 'when you have the exact bundle hash' or 'for fuzzy lookups use another tool'. The description is purely functional and offers no selection criteria or exclusions.

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

All crosscheck toolsInspect
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