get_watchlist
Read-only
Return one watchlist with its resolved company members. Free.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Watchlist id. |
signals
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- Added
TDQS
A3.7/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the read-only and non-destructive nature of the tool. The description adds 'resolved company members' as a return detail but 'Free.' is vague and adds little behavioral context. No contradiction with annotations.
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?
The description is very short and front-loaded with the core purpose. The standalone 'Free.' sentence is ambiguous and arguably unnecessary, but overall the description avoids fluff and is easy to parse.
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 read-only lookup, the description is reasonably complete with annotations covering safety. It clarifies the return content ('resolved company members'), which is useful since no output schema exists.
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 schema already documents the single parameter 'id' with description 'Watchlist id,' giving 100% coverage. The description does not add significant parameter semantics beyond implying a single watchlist is fetched.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function with a specific verb and resource: 'Return one watchlist with its resolved company members.' This distinguishes it from sibling tools like list_watchlists (plural) and add_to_watchlist/remove_from_watchlist (mutations).
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 description implies usage for retrieving a specific watchlist by ID, but it does not explicitly mention when to use it over alternatives or provide any exclusions. The context is clear but guidance is minimal.
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.
TDQS
A4/5.0
Disambiguation5/5
Each tool targets a clearly distinct resource or action: event types (acquisitions, funding_events, exec_moves), entities (companies, investors), and watchlist operations. The watchlist CRUD commands are separated by function, and company_timeline is clearly scoped to a single company's full history.
Naming Consistency4/5
Watchlist tools consistently use verb_noun (create_watchlist, get_watchlist, add_to_watchlist), while data lookup tools use plural nouns describing the returned entity or event (companies, investors, funding_events). The mixed convention is readable and predictable, with only company_timeline deviating from both patterns.
Tool Count5/5
With 11 tools, the server is well-scoped for its domain: company/event data search plus watchlist management. Each tool has a defined role and the count feels neither sparse nor bloated.
Completeness4/5
The toolset covers the core domain well: company and investor search, major event types, company timelines, and full watchlist membership management. A notable minor gap is the absence of a delete_watchlist tool, since create/list/get/add/remove exist for watchlists.