Skip to main content
Glama

analyze_force

Evaluate recorded contact-force CSV runs to detect jamming and insertion, measure peak/steady force and contact time, and map CSV columns—no robot needed.

Instructions

Offline verdict on a recorded contact-force run (peg-in-hole, press, push; CSV): jammed or not, inserted or not, peak and steady force, time in contact. Needs no robot. cols maps CSV columns, e.g. t=time,f_axial=Fz.

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": {
      "path": "<path>"
    },
    "name": "analyze_force"
  }
}

Input Schema

NameRequiredDescriptionDefault
colsNo
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the important traits: it is offline, requires no robot or live connection, and produces specific verdicts rather than raw data. It omits failure behavior (malformed CSV, missing columns) and whether anything is written to disk, which keeps it below a 5.

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?

Three compact clauses, front-loaded with the verdict purpose, then scope, then the parameter hint. Every sentence adds information and none restates the tool name.

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 two-parameter analysis tool with no output schema, the description usefully enumerates the returned quantities and the input format. Remaining gaps are output structure (dict vs. text) and force units, which are minor but would help an agent interpret results.

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?

Schema coverage is 0%, so the description must compensate, and it does for the non-obvious parameter by giving concrete column-mapping syntax ("t=time,f_axial=Fz"). The `path` parameter is only implied via the CSV mention rather than explicitly described as the file path to analyze.

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?

States a specific verb and resource: an offline verdict on a recorded contact-force CSV run, with the concrete domains named (peg-in-hole, press, push) and the exact answers returned (jammed, inserted, peak/steady force, time in contact). An agent can distinguish this from trajectory or diagnostic siblings without opening the schema.

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?

"Offline... Needs no robot" establishes the operating context clearly and the named task types scope which recordings apply. It stops short of naming an alternative tool or stating exclusions, so it is clear context without routing guidance.

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