Skip to main content
Glama

TAGLI - Branded Promotional Products

get_capabilities

שליפת יכולות ייצור, מכונות, שיטות מיתוג וטכנולוגיות מפעל. Factory machinery, UV, DTF, Pad printing, and lasers.

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_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations at all, the description bears the full disclosure burden, and it does convey that this is a read of static factory capability data with the technologies covered. It does not state whether results are account-specific, cached, or what shape the payload takes, so the read-only / safety profile is only implied by the verb 'שליפת' (retrieval).

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 short sentences, purpose front-loaded. The second sentence is largely a re-enumeration of the first's 'טכנולוגיות מפעל' in concrete terms, which is useful disambiguation rather than pure waste, though it duplicates the list slightly.

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 zero-parameter tool this is close to sufficient: the agent knows what subject matter comes back and can recognize the domain vocabulary. With no annotations and no output schema, however, the description should say more about the returned structure or grouping (capabilities vs. machines vs. technologies) than a flat example list.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to add and the baseline of 4 applies. Nothing in the description conflicts with the empty object 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?

The description names a specific verb (שליפת / retrieval) and resource (production capabilities, machines, switching methods, factory technologies), then grounds it with concrete examples (UV, DTF, Pad printing, lasers). It is clearly a static reference/config lookup, distinct from transactional siblings like get_product or agentic_quote, though it never explicitly contrasts itself with get_business_profile.

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?

There is no when-to-use guidance: nothing tells the agent whether to call this before quoting, which sibling it substitutes for, or whether the data is per-tenant or global. The Hebrew and English halves are restatements of the same resource rather than usage instructions.

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