Skip to main content
Glama

Corey James portfolio

scale

The size of the body of work: source lines, commits, languages, systems, stories, ideas, tools, patent applications, and the agent gallery's roles, functions and specialists (counted separately).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations and no output schema, the description carries the full burden and does not state that this is a read-only aggregate, what the response looks like (a set of counts? a single total?), or whether the numbers are computed live. It does add one genuine behavioral detail — the agent gallery's roles, functions and specialists are 'counted separately' — which is real value beyond structured fields, but it is the only such detail.

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?

A single front-loaded sentence with no filler; the closing parenthetical about separate counting is well placed. The long comma enumeration is dense but each item contributes to defining scope, so little could be cut without losing coverage.

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 zero-parameter aggregate with no output schema, the agent still lacks the essentials: what shape the result takes, whether counts are per-category objects or a scalar, and how the separately-counted gallery figures are keyed. The description defines the domain well but leaves the return contract entirely unspecified.

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 there is nothing for the description to disambiguate and the baseline is 4. The enumeration does clarify the *scope* of what is counted, which is the closest analogue to parameter semantics here.

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

Purpose3/5

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

The description names a specific resource — the aggregate size of the 'body of work' — and enumerates what it covers (source lines, commits, languages, systems, stories, ideas, tools, patent applications, agent gallery roles). But it is a noun phrase with no verb, so the agent must infer that the tool *returns counts* rather than listing or searching those things. It is distinguishable from the list_* siblings only by implication (aggregation vs. enumeration), not by an explicit statement.

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 call this versus the many siblings such as list_systems, list_ideas, list_patent_applications, or search_portfolio. An agent could reasonably read the enumeration of 'systems, ideas, tools, patent applications' as overlapping with those listing tools, and nothing in the description resolves that ambiguity.

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