Skip to main content
Glama
Sign In
Refract

Refract

by LoudiliMed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

expand

Takes a Python file and specified function/class names, returns their full source code along with compressed dependency context.

Instructions

Given function/class names in a .py file, return them verbatim (full source) plus their compressed dependency context.

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": {
      "file_path": "<file_path>",
      "targets": "<targets>"
    },
    "name": "expand"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetsYesFunction/class names to expand.
file_pathYesPath to a .py file (relative to --root or absolute).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations are absent, so description carries full burden. It states it returns 'full source' and 'compressed dependency context', which is a key behavioral trait. However, it does not disclose read-only nature, auth requirements, or potential performance implications (e.g., large files). Adequate but not comprehensive.

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?

Single sentence, front-loaded with purpose. No wasted words; all information is necessary and directly conveys the tool's action and output.

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?

Given that there is no output schema and no annotations, the description is somewhat vague about the exact format of 'compressed dependency context'. While the tool is simple, the description could be more complete by clarifying what 'compressed' means. Sufficient but leaves room for ambiguity.

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%, so the schema already documents both parameters adequately. The tool description adds no new meaning beyond restating the schema descriptions, meeting the baseline but not adding value.

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?

Description uses specific verb 'expand' on function/class names in a .py file, clearly indicating it returns full source plus dependency context. Differentiates from siblings like 'get_compressed' (which likely returns compressed content) and 'blast_radius' (impact analysis).

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?

No explicit guidance on when to use this tool versus alternatives like 'get_compressed' or 'blast_radius'. Usage is implied by the description (to get full source of specific definitions with dependencies), but lacks when-not-to-use or prerequisite information.

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