Skip to main content
Glama
Sign In
AIMFP

AIMFP

by aryanduntley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

update_function_file_location

Idempotent

Update the file location of a function by specifying the function ID, current file ID, and new file ID.

Instructions

Move function to different file (rarely used)

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": {
      "function_id": "<function_id>",
      "old_file_id": "<old_file_id>",
      "new_file_id": "<new_file_id>"
    },
    "name": "update_function_file_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
function_idYesFunction ID to move
old_file_idYesCurrent file ID
new_file_idYesNew file ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.37.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=true, but the description adds no supplementary behavioral details. It does not disclose whether moving a function affects references, requires permissions, or has side effects. No contradiction with annotations.

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?

The description is extremely short (five words), which is concise but lacks structure. Every word earns its place, but the brevity omits important information. A longer, more structured description would improve usability without being wasteful.

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?

Given the tool's three parameters and no output schema, the description is too sparse. It does not explain the effect of moving a function, potential constraints, or what happens to related objects. More context is needed for effective use, especially given the complex domain and many sibling tools.

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?

The input schema covers all three parameters with clear descriptions, achieving 100% coverage. The tool description adds minimal meaning beyond the schema, simply restating the action. Baseline 3 is appropriate as the schema already provides adequate semantics.

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?

The description clearly states the verb 'Move' and the resource 'function to different file', distinguishing it from sibling tools like update_function or update_file. The 'rarely used' qualifier adds context, though it does not elaborate on the scope or impact of the move.

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?

The description only notes that the tool is 'rarely used', but provides no explicit guidance on when to use this tool versus alternatives, such as update_function or when to move functions vs. other operations. No when-not-to-use or prerequisite information is given.

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