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?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that results mirror 'the kit page' listing at file granularity, which is modest extra context, but says nothing about ordering, pagination, or behavior for an unrecognized kit name.

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 core action in the first sentence, followed by a compact enumeration of accepted kit names. Both sentences earn their place, though the value list could have been attached to the parameter rather than left in the description body.

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?

An output schema exists, so return values need no explanation, and the tool is a single-parameter read with a simple behavior. The description covers what it returns plus the full set of valid inputs, leaving nothing an agent needs in order to invoke it correctly.

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% and the property description only offers partial examples ('Job Cost or Commission'), so the description earns credit for enumerating the valid kit names (Job Cost Standard, Production Standard, Appointment Standard, Commission Standard, Complete Standard), effectively supplying the missing enum. It does not clarify whether the short form or 'The ... Standard' form is required for the input value.

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?

"Returns the file-by-file contents of a Company Framework kit, as the kit page lists it" gives a specific verb (returns) and resource (kit contents) plus a useful granularity cue (file-by-file). It stops short of naming which sibling to use instead (e.g. search_company_framework), so the differentiation is implicit rather than explicit.

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 only implied: an agent can infer this is the lookup to call when it already knows a kit name and wants the itemized file list. There is no explicit when-to-use, when-not-to-use, or comparison against search_company_framework or other framework-related siblings.

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