Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

run_contacts

Read-only

Retrieve contact counts, robot contacts, or optional overlap counts from a completed simulation run to validate interactions and check expected contacts without measuring penetration.

Instructions

Page recorded contact_counts, robot_contacts, or optional overlap_counts from a completed run. Overlap counts include expected contacts and do not measure penetration.

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": {
      "job_id": "<job_id>"
    },
    "name": "run_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
job_idYes
offsetNo
categoryNocontact_counts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine semantic context beyond that: overlap_counts include expected contacts and explicitly do not measure penetration, which prevents a common misreading of the returned numbers. It does not disclose pagination behavior or what happens when offset exceeds the recorded count.

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 compact sentences with no filler, and the resource list is front-loaded before the caveat. The verb "Page" is slightly informal and the sentence packs three category names inline, but nothing is wasted.

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?

With no output schema, the description is the only place an agent can learn what comes back, and it names the record types but not their shape or how paging terminates. It covers the key semantic trap (overlap counts are not penetration) yet leaves the retrieval mechanics underspecified for a four-parameter paged tool.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden, and it only partially delivers. It supplies the meaningful values for the category parameter (contact_counts, robot_contacts, overlap_counts) — valuable since the schema defines no enum — but says nothing about job_id semantics, limit, or offset defaults and paging interaction.

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?

"Page recorded contact_counts, robot_contacts, or optional overlap_counts from a completed run" gives a specific verb (page/retrieve) plus the exact resource families returned, which is more than a restatement of the name. It does not explicitly differentiate itself from siblings such as run_observe or run_verify, so an agent must infer the boundary from the resource names alone.

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

Usage Guidelines3/5

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

The phrase "from a completed run" establishes a prerequisite state, implying this is a post-run retrieval tool rather than something to call mid-execution. However, it names no alternative and gives no explicit when-not guidance (e.g., what to call for an in-progress run, or which category to prefer).

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