Skip to main content
Glama
Sign In

VergeCommon

by io.github.jdhart81
OverviewDiscussionsAdmin

vergecommon_capabilities

Read-onlyIdempotent

Use first when you are unsure what VergeCommon can do on this connection: it says which tools are available, what this connection cannot do, and whether a personal agent token is in use. Do not use it to find co-ops or to calculate anything; use list_public_coops or the pooling draft tools for that. Returns the service origin, access level, token scopes, lists of available and unavailable capabilities and a short note, plus a source receipt and a link to start a co-op.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: it discloses that the result reveals the caller's access level, token scopes, whether a personal agent token is in use, and which capabilities are unavailable on this connection. Lacking only details like failure behavior when unauthenticated.

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?

Front-loaded with the selection cue ('Use first when you are unsure...'), followed by the negative routing and then the return contents. Three sentences, all load-bearing; the final return enumeration is a slightly long list but is justified because no output schema exists to carry it.

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?

With zero parameters and no output schema, the description carries the full burden of explaining returns, and it does so thoroughly (service origin, access level, token scopes, capability lists, note, source receipt, co-op link). An agent has everything needed to call it and interpret the response.

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 takes zero parameters, so per the baseline this sits at 4. The description correctly adds no parameter narrative, which is appropriate for a no-argument introspection call.

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?

States a specific verb+resource: it reports what tools are available, what the connection cannot do, and whether a personal agent token is in use. It explicitly separates itself from siblings (list_public_coops, pooling draft tools), so an agent can identify it as the discovery/capabilities tool without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('Use first when you are unsure what VergeCommon can do on this connection') and explicit exclusions ('Do not use it to find co-ops or to calculate anything'), each paired with the correct alternative tool. Nothing about when-to-use is left to inference.

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

All VergeCommon 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