Skip to main content
Glama

saved_companies

Manage a local company list for job searches: list, add, or remove companies, with all data stored only on this computer.

Instructions

List, add or remove companies in your saved list (used by search_jobs). The list is stored only on this computer.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "saved_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNolist
companyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior5/5

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

The description discloses that the list is 'stored only on this computer,' which is a crucial behavioral trait regarding data persistence and scope, especially since no annotations were provided.

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 definition is appropriately sized and front-loaded, conveying the core function and location constraint immediately without redundant phrasing.

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?

Given the low complexity and lack of output schema, the definition is highly complete by addressing the action set, usage context, and storage mechanism.

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

Parameters1/5

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

The description fails to add semantic meaning to the parameters 'action' or 'company.' With 0% schema description coverage, the description must compensate for the lack of parameter detail, which it does not do.

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 clearly identifies the resource (companies) and the specific actions (list, add, remove) supported by the tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

By stating the list is 'used by search_jobs,' the description provides explicit guidance on the intended context and how this tool relates to other capabilities in the system.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.