Skip to main content
Glama
Sign In
Agent.ai MCP Server

Agent.ai MCP Server

by OnStartups
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

company_research_v2_list_tracked

Retrieve a list of companies you are tracking. Filter by favorites, search query, or tags to narrow results.

Instructions

Get all companies tracked by the user.

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": {
      "output_variable_name": "<output_variable_name>"
    },
    "name": "company_research_v2_list_tracked"
  }
}

Input Schema

NameRequiredDescriptionDefault
favorites_onlyNoOnly return favorite companies.
searchNoFilter by company name or domain.
tagsNoFilter by tags (comma-separated).
output_variable_nameYesVariable name for the tracked companies list.tracked_companies

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It merely states the function without disclosing behavioral traits like pagination, sorting, or behavior when no companies are tracked.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is concise but omits necessary details about filtering parameters and return value. It is appropriately short but lacks completeness for effective use.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 4 parameters, no output schema, and no annotations, the description is too brief. It fails to explain filtering options or output format, leaving agents uncertain about usage.

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?

Schema coverage is 100% with well-described parameters. The description adds no additional meaning beyond the schema, resulting in baseline score.

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 states the tool retrieves all companies tracked by the user, distinguishing it from sibling tools like search_companies which finds new companies. However, it does not explicitly differentiate itself from similar list operations.

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?

No guidance on when to use this tool versus alternatives like company_research_v2_search_companies or company_research_v2_track_company. The context is implied but not stated.

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

Deploy Server

Other Tools