Skip to main content
Glama

Company Framework

Search (for ChatGPT)

search
Read-only

Searches companyframework.com and returns result ids, titles and URLs, in the shape that ChatGPT connectors and deep research use.

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

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to search for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered, and the description adds value beyond that by disclosing the return shape (ids, titles, URLs) and the output format compatibility with ChatGPT connectors/deep research — useful for an agent deciding downstream handling. Gaps remain: no mention of result count, pagination, ranking, or whether the query syntax supports anything beyond plain text.

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?

A single front-loaded sentence with no waste: the action, the target site, and the return shape are all delivered immediately.

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 one-parameter, annotation-covered search tool with no output schema, the description covers the essentials, including the return shape that would otherwise be unknown. The missing piece is disambiguation from the closely named sibling, which matters given the catalog provided.

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?

With only one parameter and 100% schema description coverage ('What to search for'), the schema already carries the parameter semantics. The description adds nothing further about query format, operators, or length limits, so the baseline 3 applies.

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 states a specific verb and resource ('Searches companyframework.com') and even names what it returns (ids, titles, URLs), so an agent knows exactly what the call does. It does not, however, differentiate itself from the near-identically named sibling 'search_company_framework' or explain how the two differ in scope.

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 explicit when-to-use, when-not-to-use, or alternative routing guidance. The only implied context is that this hits companyframework.com, and the phrase 'in the shape that ChatGPT connectors and deep research use' hints at a consumer but does not say when to prefer this over 'search_company_framework' or 'ask_jd'.

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