Skip to main content
Glama
firelock-ai

kin

Official
by firelock-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

get_context_pack

Read-onlyIdempotent

Bundle code bodies, signatures, and relationship routes around specified entities or a question to supply context for repository analysis.

Instructions

Bodies, signatures and routes around entities or a question, in one bundle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
depthNoHops to walk.
entitiesNoSeveral entities, by name or UUID.
questionNoA question to resolve into entities.
entity_idNoUUID
max_charsNoHard cap on reply bytes.
focal_bodyNoFalse: neighbourhood only, no focal body.
token_budgetNoToken budget.
neighbor_bodiesNoTrue: neighbours' bodies too, not signatures.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.7.17
    • removedInput schema / anyOf
      Removed value: -[
-  {
-    "required": [
-      "entity_id"
-    ]
-  },
-  {
-    "required": [
-      "entities"
-    ]
-  },
-  {
-    "required": [
-      "question"
-    ]
-  }
-]
    • changedInput schema / properties / depth / description
      Previous value: -"Dependency traversal depth"New value: +"Hops to walk."
    • changedInput schema / properties / entities / description
      Previous value: -"Several focal entity names or UUIDs when the question is about how they connect."New value: +"Several entities, by name or UUID."
    • changedInput schema / properties / entity_id / description
      Previous value: -"Focal entity UUID"New value: +"UUID"
    • addedInput schema / properties / focal_body
      Added value: +{
+  "default": true,
+  "description": "False: neighbourhood only, no focal body.",
+  "type": "boolean"
+}
    • changedInput schema / properties / max_chars / default
      Previous value: -12000New value: +24576
    • changedInput schema / properties / max_chars / description
      Previous value: -"Serialized characters this response may occupy; what was cut is named in `elisions`."New value: +"Hard cap on reply bytes."
    • addedInput schema / properties / neighbor_bodies
      Added value: +{
+  "default": false,
+  "description": "True: neighbours' bodies too, not signatures.",
+  "type": "boolean"
+}
    • changedInput schema / properties / question / description
      Previous value: -"A plain-language question resolved to one or more focal entities before packing."New value: +"A question to resolve into entities."
    • changedInput schema / properties / token_budget / default
      Previous value: -2500New value: +4000
    • changedInput schema / properties / token_budget / description
      Previous value: -"Token budget (8000, 16000, or 32000)"New value: +"Token budget."
  2. First observedv0.7.16

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds that results come as one bundled payload rather than a graph walk, but says nothing about cost, truncation behavior tied to max_chars/token_budget, or what is omitted when budgets are hit.

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?

It is a single short sentence with no waste, which is good, but the terseness tips into under-specification for an 8-parameter tool. Nothing is padded, yet the one clause carries too little to orient the agent.

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?

For an 8-parameter tool with no output schema, the description should clarify mutual exclusivity of entities/question/entity_id and what the returned bundle looks like. Five input modes (entities, question, entity_id, depth, budget toggles) are left entirely to the schema, so the definition is not complete enough to call this correctly.

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% across all 8 parameters, so the schema already explains depth, entity_id, max_chars, token_budget and the two boolean toggles. The description only gestures at the entities-vs-question input modes and adds no syntax, default, or interaction detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the payload it returns ("bodies, signatures and routes") and the anchor ("entities or a question"), which is more specific than a tautology. But it gives no verb, and the phrase "around entities" is vague about what the bundle actually is, so an agent cannot cleanly distinguish it from siblings like graph_neighborhood or get_entity_source without opening the schema.

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?

There is no when-to-use guidance and no mention of alternatives, despite several plausible siblings (graph_neighborhood, semantic_search, get_entity_source). The agent must infer from the name alone that this is the 'give me a code bundle' entry point.

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