Skip to main content
Glama
mrorigo
by mrorigo

get_function_metadata

Retrieve detailed metadata for any function using its fully qualified name to analyze code structure and relationships.

Instructions

Retrieve metadata for a specific function by its fully qualified name.

Args: fqn: The fully qualified name of the function to retrieve metadata for. Returns: MetadataResponse containing detailed function metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fqnYesFully qualified name of the function

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
nlocYes
summaryYes
is_asyncYes
line_endYes
docstringYes
file_pathYes
hash_bodyYes
is_methodYes
is_staticYes
class_nameYes
complexityYes
decoratorsYes
line_startYes
parametersYes
is_exportedYes
return_typeYes
incoming_edgesYes
is_entry_pointYes
outgoing_edgesYes
access_modifierYes
analysis_statusNo
catches_exceptionsYes
fully_qualified_nameYes
external_dependenciesYes
local_variables_declaredYes
Behavior3/5

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

No annotations provided; description implies a read-only operation but gives no details on permissions or side effects. Adequate for a simple retrieval tool.

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 sentences plus structured Args/Returns. No redundant information, efficient.

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

Completeness4/5

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

Given low complexity (1 param, output schema exists), the description is sufficient. No missing critical information.

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%, and description repeats the parameter's meaning. No additional semantic detail beyond the schema.

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?

Description clearly states 'Retrieve metadata for a specific function' with verb and resource. It does not explicitly differentiate from siblings, but the purpose is clear.

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 guidance on when to use this tool vs alternatives. No context about filtering, searching, or listing functions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mrorigo/code-flow-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server