Skip to main content
Glama

Company Framework

What is in a kit

kit_contents
Read-only

Returns the file-by-file contents of a Company Framework kit, as the kit page lists it. Kits: The Job Cost Standard, The Production Standard, The Appointment Standard, The Commission Standard, The Complete Standard.

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": {
      "kit": "<kit>"
    },
    "name": "kit_contents"
  }
}

Input Schema

NameRequiredDescriptionDefault
kitYesThe kit's name, for example Job Cost or Commission.

Output Schema

NameRequiredDescriptionDefault
kitYes
urlNo
titleYes
contentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safe read-only nature is covered without the description repeating it. The description contributes by clarifying the result mirrors the kit page's listing, which hints at ordering and presentation. It says nothing about permissions, limits, or behavior when an unknown kit name is supplied, and an output schema already documents the return shape.

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?

Two sentences, and the operative purpose is front-loaded before the kit enumeration. The list is dense but each item is a permitted input value rather than filler, so every token earns its place.

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?

For a single-parameter read tool with full schema coverage, an output schema, and safety annotations, the definition covers the essentials: what it returns, how it is scoped, and which kit names are valid. The only gap is what happens when the requested kit does not exist or what to do instead for content search.

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?

Schema coverage is 100%, so the baseline is 3. The description goes beyond it by enumerating the recognized kit names (Job Cost Standard, Production Standard, Appointment Standard, Commission Standard, Complete Standard), which effectively supplies the missing enum values. This materially reduces the chance of passing an invalid or abbreviated name.

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 uses a specific verb and resource combination: 'Returns the file-by-file contents of a Company Framework kit.' That is far more precise than the title 'What is in a kit.' It does not name or contrast itself with the sibling search_company_framework, so an agent must infer whether this is the browse tool or the search tool.

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?

Usage is implied: call this to see which files a kit contains, 'as the kit page lists it.' There is no explicit when-to-use, no when-not-to-use, and no pointer to the sibling search_company_framework for keyword lookup across the framework. The valid kit list helps identify the correct subject but provides no guidance on choosing between tools.

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