Skip to main content
Glama

Fillio · electronics overmolding

Portal upload link

get_upload_link
Read-onlyIdempotent

Returns the address of Fillio's portal, where the user uploads a 3D file, gets the feasibility analysis and requests a quote, with the steps and what to have at hand. Read-only: nothing is created or sent.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_upload_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: “fr” or “en”.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description reinforces rather than contradicts them while adding the useful nuance that 'nothing is created or sent', i.e. no quote request is triggered on the user's behalf. With no output schema, the note that the answer includes the steps and what to have at hand is genuinely additive return-value context.

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?

A single front-loaded sentence leading with the actual return value, followed by the portal's purpose and a short safety clause. The trailing 'with the steps and what to have at hand' is slightly loose phrasing but still informative, so nothing needs cutting.

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?

For a one-parameter, read-only lookup with no output schema, the description covers what is returned (portal address, procedural steps, prerequisites) and the absence of side effects — the main things an agent needs. The only gap is silence on the 'lang' parameter's effect on the response language.

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?

There is a single optional 'lang' parameter with 100% schema description coverage and an explicit enum, so the schema carries the meaning. The description says nothing about the language parameter or its default behavior, which is the baseline-3 case rather than added value.

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?

States a specific verb and resource ('Returns the address of Fillio's portal') and enriches it with what the portal is for (upload a 3D file, feasibility analysis, quote request). It is clearly distinguishable from the sibling tools (capabilities, design guide, cost estimate, resin recommendations), though it never explicitly contrasts itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description frames the exact user situation that selects this tool: the user wants to hand off a 3D file, get a feasibility read and request a quote. That is clear usage context, but there are no explicit when-not conditions or named alternatives (e.g. vs. send_harness_quote_template).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources