Skip to main content
Glama

Company Framework

Search Company Framework

search_company_framework
Read-only

Searches companyframework.com: the kits, the books, prices, license, refunds, the free tools, the field notes and the Fathomed bots, plus answer pages on job costing, contractor profit and sales commission. Returns matching passages with their source URLs.

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": {
      "query": "<query>"
    },
    "name": "search_company_framework"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe question or words to look for.

Output Schema

NameRequiredDescriptionDefault
passagesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 and closed-domain profile is covered structurally. The description adds that results are 'matching passages with their source URLs', but with an output schema present that is partly redundant, and it says nothing about ranking, result limits, or behavior when a query matches nothing on the site.

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?

Two sentences, front-loaded with the verb and the site domain, followed by the content scope and return shape. The long mid-sentence enumeration is dense but each item adds routing information, so little is wasted beyond the slightly list-like cadence.

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?

For a one-parameter read-only search tool, everything an agent needs is present: the source corpus, the topics covered, and the return shape, with annotations covering safety and an output schema covering result structure. Nothing required to invoke it correctly is missing.

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

Parameters3/5

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

There is a single parameter with 100% schema description coverage ('The question or words to look for.'), so the schema already carries the meaning and the baseline is 3. The topic enumeration in the description implicitly helps formulate a query, but no extra syntax, phrasing guidance, or length limits are offered beyond the schema.

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 (searches) bound to a specific resource (companyframework.com) and then enumerates the content domains covered: kits, books, prices, license, refunds, free tools, field notes, Fathomed bots, and answer pages on job costing, profit, and commission. That enumeration is what separates it from a generic sibling like 'search' or 'ask_jd', so an agent can route without opening a schema.

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 by the content inventory: the topics listed tell an agent this is the tool for questions about products, pricing, licensing, and refunds. However, there is no explicit when-to-use statement, no exclusion, and no named alternative such as 'search' or 'ask_jd', so the agent must infer routing from the topic list alone.

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