Skip to main content
Glama

Get Team Entry by ID

team_get_entry_by_id
Read-onlyIdempotent

Fetch a specific team entry by ID to view full details, relationships, and importance score for project memory and dependency tracking.

Instructions

Get a specific team entry by ID with full details including relationships and importance score. Requires TEAM_DB_PATH.

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": "team_get_entry_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
entry_idNo
use_test_dbNo
workspace_idNoOptional workspace isolation identifier (e.g. "alpha"). Do not use numeric project IDs or "workspace" as the key.
project_numberNo
include_relationshipsNo

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
entryNo
errorNoHuman-readable error message
detailsNoAdditional error context
successNo
categoryNoError category (validation, query, connection, internal)
importanceNo
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
relationshipsNo
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv9.1.0
    • addedOutput schema / properties / importance / properties / breakdown / properties / trustModifier
      Added value: +{
      +  "type": "number"
      +}
  2. First observedv9.0.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the TEAM_DB_PATH prerequisite and hints at response richness ('relationships and importance score'), but says nothing about behavior on a missing or invalid ID.

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?

Two short sentences, front-loaded with the purpose and then the data returned. No wasted wording, though the second sentence is a bare prerequisite rather than part of a coherent usage narrative.

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?

An output schema and rich annotations remove the need to explain returns and safety, but four of five loosely-typed, mostly undocumented parameters remain unexplained, and the interaction between entry_id, project_number and workspace_id is left entirely ambiguous.

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

Parameters2/5

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

Five parameters with only 20% schema description coverage, and the description contributes nothing about any of them — not entry_id's accepted number/string types, include_relationships defaulting to true, project_number, or use_test_db. With low schema coverage, the description needed to compensate and does not.

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?

States a specific verb and resource ('Get a specific team entry by ID') and signals the payload ('full details including relationships and importance score'). It is distinguishable from team_search/team_semantic_search by the ID-based lookup, though it does not address the near-identical sibling get_entry_by_id.

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 statement of when to use this versus the search tools (team_search, team_semantic_search, search_entries) or the plain get_entry_by_id sibling. The only guidance is an environment prerequisite ('Requires TEAM_DB_PATH'), which is configuration, not usage routing.

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