Skip to main content
Glama
Sign In
ya-tracker-mcp

ya-tracker-mcp

by imdeniil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_entity

Retrieve a project, portfolio, or goal by ID to access its details.

Instructions

Get a project, portfolio, or goal by ID.

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": {
      "entity_type": "<entity_type>",
      "entity_id": "<entity_id>"
    },
    "name": "get_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoOptional list of fields to return. Use ["all"] for all fields.
entity_idYesEntity ID
entity_typeYes"project", "portfolio", or "goal"
output_formatNoResponse format: "text" (default, markdown) or "json"text
full_descriptionNoIf true, do not truncate description (default false)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. While 'Get' implies a read operation, the description provides no detail on error behavior, auth requirements, or any side effects. It does not add context beyond the verb and resource.

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 clear sentence, front-loaded with the action and resource. Every word earns its place with no fluff or repetition.

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

Completeness3/5

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

The tool is simple (get-by-ID) and an output schema exists, so the description need not explain return values. However, it lacks any context about optional parameters like fields or full_description, and does not clarify when these might be used. For a 5-parameter tool, it is minimally complete.

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%, so parameters are already well-documented. The description does not add extra semantics beyond the schema; it simply restates the purpose of entity_id/entity_type. Baseline 3 is appropriate.

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 uses a specific verb ('Get') and resource ('project, portfolio, or goal') with an explicit lookup mechanism ('by ID'). This clearly distinguishes it from sibling tools like search_entities or create_entity.

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 (fetch a single entity when you have an ID) but does not explicitly state when to prefer this over search_entities or provide exclusions. It offers no comparison to alternatives, so guidance is only implicit.

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