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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and the closed-corpus nature are covered structurally; the description usefully confirms the bounded corpus by naming the site and its content areas. It does not disclose result-count limits, ranking/snippet behavior, pagination, or whether the query is matched semantically or by keyword (faintly hinted by the schema's 'question or words'). That is a modest value-add on top of annotations, not a rich one.

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 target site, followed by a dense but purposeful corpus inventory and a return-shape note. Nothing is redundant, though the long comma-spliced enumeration is slightly harder to scan than a structured list would be.

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?

An output schema exists, so the one-clause note about returning passages with source URLs is sufficient and return values needn't be elaborated. With one fully documented parameter and safety carried by annotations, the definition leaves little essential ambiguity — the remaining gap is routing guidance among siblings, not tool mechanics.

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 required parameter with 100% schema description coverage, so the schema already documents it fully. The description adds nothing about query phrasing, length, or whether natural-language questions are supported beyond the enumeration of topic areas. Baseline 3 is the correct ceiling here.

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 gives a specific verb ('Searches') bound to a named resource (companyframework.com) and then enumerates the corpus it covers: kits, books, prices, license, refunds, free tools, field notes, Fathomed bots, and answer pages on job costing/profit/commission. That is far more informative than a bare restatement. It stops short of 5 because it never draws a line against the obviously near-identical sibling 'search' or against 'ask_jd'/'fetch', so the agent must still guess which search surface to use.

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 tool for questions about Company Framework's products, pricing, and contractor-topic answer pages. There is no explicit statement of when to prefer this over 'search', 'ask_jd', or 'fetch', and no note about what to do when no passages match. Adequate but with a clear gap given the crowded sibling set.

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