Skip to main content
Glama
Sign In
keyso-mcp

keyso-mcp

by abukreev-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

keyso_get_ai_tracker_id_entity

Fetch complete details for an AI tracker project entity, including search settings, update schedule, and alert configurations, to review and manage monitoring.

Instructions

Трекер ИИ - сущность проекта Method: GET Path: /ai_tracker//entity Возвращает полное описание сущности проекта, включая настройки поиска, расписания обновления и оповещений. Пример запроса https://api.keys.so/ai_tracker/<id>/entity

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": {
      "id": "<id>"
    },
    "name": "keyso_get_ai_tracker_id_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesin: path (auto-detected)
tokenNoAPI token override (fallback: KEYSO_TOKEN env)
base_urlNoOverride API base URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It explicitly states 'Method: GET', gives the full path, and says the response includes search settings, update schedules, and notifications, making clear this is a read-only entity lookup. It does not discuss auth or rate limits, but the schema already exposes token and base_url parameters for authentication.

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 compact and well structured: a resource label, method/path, one sentence about return content, and an example URL. Every element is useful, and the key facts appear early.

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 GET entity endpoint with no output schema, the description is reasonably complete: it provides method, path, example, and return-value categories. It omits response shape details, but those are not essential for correctly invoking this low-complexity read operation.

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 description coverage is 100% for id, token, and base_url, so the baseline of 3 applies even though the description adds no parameter-specific meaning. The path template partially reinforces the role of id.

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 action and resource: it 'returns the full description of the project entity' and enumerates content such as search settings, update schedules, and notifications. This distinguishes it from chart/report/dates siblings in substance, though it does not explicitly name a competing tool.

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 use case is implied: if the agent needs the full project-entity description, this is the endpoint. However, there is no explicit when-to-use or when-not-to-use guidance, and no alternatives are mentioned despite many closely related AI-tracker sibling tools.

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