Skip to main content
Glama

assura_infer

Infer skeleton Assura contracts from inline Rust source code or a .rs file to prepare Rust programs for formal verification.

Instructions

Infer skeleton Assura contracts from Rust source code. Provide either source (inline Rust) or file (path to .rs file).

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": "assura_infer"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoPath to a Rust (.rs) file. Provide either `source` or `file`.
sourceNoRust source code to infer contracts from (inline). Provide either `source` or `file`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add real signal by calling the output 'skeleton' contracts, implying draft/inferred rather than validated results, but it says nothing about whether files are written, how parse failures surface, or what the result looks like.

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?

Two tight sentences with the purpose front-loaded and the input-selection rule immediately after. No filler or redundant restatement.

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 and no annotations, the description should say something about the return shape of the inferred contracts (text blob, file path, structured IR). The input side is fully covered, but the output side is left to inference.

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?

Schema coverage is 100% and both parameters already document the either/or constraint, so the description largely repeats the schema. Baseline 3 applies since the schema does the heavy lifting and the description adds no format or precedence detail.

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 gives a specific verb ('Infer') and resource ('skeleton Assura contracts from Rust source code'), which is enough to distinguish it from siblings like assura_check or assura_explain. It does not explicitly contrast against those siblings, but the action is unambiguous.

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?

It states the input choice clearly ('Provide either `source` (inline Rust) or `file`'), which is useful guidance, but gives no indication of when to pick this tool over assura_check or assura_explain, nor any prerequisites such as needing existing Rust code.

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