Skip to main content
Glama

skillporter_context

Read-only

Inspect active instruction files, ignored foreign files, reachable skills, and startup token budget for a specific harness before running an agent.

Instructions

[READ] Inspect exact active instruction files, ignored foreign files, reachable skills, and startup token budget for a specific harness.

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": {
      "harness": "<harness>"
    },
    "name": "skillporter_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo.
harnessYesTarget harness ID (e.g. claude-code, codex, cursor)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.0

TDQS

B3.3/5.0
Behavior3/5

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

readOnlyHint already declares that this is a safe read, and the [READ] tag just repeats that. The description does add real detail beyond the annotations: it names the returned sections and, notably, that ignored foreign files are reported, so an agent can expect a report of both active and filtered items. It says nothing about cost, caching, or output shape, and no output schema exists to cover that gap.

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?

One dense sentence, front-loaded with the [READ] tag and the verb, with four resources listed in parallel. Nothing is wasted and nothing is buried.

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?

For a two-parameter read-only tool with no output schema, the agent mostly knows what it will get back. The complete silence on `path` semantics, and the absence of any pointer to the similar inspect, detect, or status siblings, leave real gaps for correct invocation.

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?

The description reinforces the required `harness` parameter ('for a specific harness'), which the schema already documents. But the `path` parameter, which controls which project root is inspected, appears in neither the description nor the schema; coverage is only 50%, so the description should have compensated 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?

A specific verb of inspection plus four enumerated resources (active instruction files, ignored foreign files, reachable skills, startup token budget) scoped to one harness. That is far more informative than a generic inspect, but it never clarifies how it differs from the similar sibling tools, skillporter_inspect, skillporter_detect, and skillporter_status.

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 implied usage is clear: call this tool when you need to know what is actually active for a given harness, including what was filtered out. But the description gives no explicit guidance on when to use this tool instead of skillporter_inspect or skillporter_detect, and names no prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.