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

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

Annotations already establish that this is a read-only, non-destructive search. Beyond that, the description usefully discloses the return shape (ids, titles, URLs) and connector compatibility, which matters because there is no output schema. It still omits result limits, pagination, and ranking behavior, so it is not fully comprehensive.

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?

The description is a single front-loaded sentence with no filler. It efficiently covers the site searched, returned fields, and intended integration shape without burying the important information.

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 simple one-parameter search tool with annotations covering safety and no output schema, the description provides enough context to invoke it correctly. It could be more complete by stating result limits or ranking/pagination behavior, but the core return format is present.

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?

The single query parameter is fully documented in the schema as 'What to search for.' The description adds no syntax, matching behavior, or query-format details beyond that, so it does not meaningfully improve parameter understanding over the 100% schema coverage.

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 names the returned fields ('result ids, titles and URLs'). That is clear, but it does not explicitly differentiate the tool from the sibling search_company_framework beyond the ChatGPT/deep-research result shape.

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?

The mention of 'ChatGPT connectors and deep research' implies a usage context, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative. The agent must infer when this search endpoint is preferable to sibling search 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