Skip to main content
Glama

assura_ir_prompt

Render an AI prompt to generate an Implementation IR (.ir sidecar) for an Assura contract using inline source or a file, with optional declaration and pattern selection.

Instructions

Render an AI prompt to generate Implementation IR (.ir sidecar) for an Assura contract. Provide source or file, optional decl, and pattern (auto by default).

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

Input Schema

NameRequiredDescriptionDefault
declNoDeclaration name (required when the file has multiple verification jobs).
fileNoPath to an .assura file. Provide either `source` or `file`.
sourceNoAssura source (inline). Provide either `source` or `file`.
patternNoPattern overlay: auto, identity, arithmetic, length-copy, call-chain, bounds-check, field-accessauto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It states that the tool renders a prompt, but it does not disclose whether it reads files, has side effects, requires permissions, or what the returned prompt 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 sentences, front-loaded with the core action, with no wasted wording. The second sentence efficiently covers the main parameter constraints.

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?

The description is adequate for a simple four-parameter tool whose schema is fully documented, but with no annotations and no output schema it leaves behavioral context and return-value expectations unexplained.

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 description coverage is 100%, so the schema already documents all four parameters. The description only repeats the choice between `source` and `file` and notes `pattern` defaults to auto, adding no meaning beyond what the schema provides.

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 and resource: 'Render an AI prompt to generate Implementation IR (.ir sidecar) for an Assura contract.' It makes clear this produces a prompt rather than generating IR directly, but it does not explicitly contrast itself with siblings like assura_ir_verify or assura_infer.

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?

Usage is implied by the stated purpose and the note to provide `source` or `file`, but there is no explicit when-to-use guidance, no when-not-to-use conditions, and no mention of alternatives such as assura_ir_verify.

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