Skip to main content
Glama
Sign In
Assura

Assura

Official
by assura-lang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

assura_check

Parse, type-check, and verify Assura contracts from inline source or a .assura file, returning structured diagnostics and verification results.

Instructions

Parse, type-check, and verify an Assura contract. Returns structured diagnostics and verification results. Provide either source (inline code) or file (path to .assura 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_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoPath to an .assura file. Provide either `source` or `file`.
sourceNoAssura source code to verify (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?

With no annotations at all, the description carries the whole burden. It does disclose the return surface ("structured diagnostics and verification results"), which is useful since no output schema exists, but says nothing about whether a failing contract is an error or a normal result, whether the operation is read-only, or how large inputs are handled.

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 short sentences, front-loaded with the actions and resource, then the return value, then the input constraint. Nothing redundant or padded.

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 two-parameter tool with no annotations and no output schema, the description covers what it does and roughly what comes back, which is the minimum. It leaves open error behavior, whether both/neither of source and file is permitted, and how to differentiate the result from the sibling verify tool.

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 are documented in the schema with the same 'source or file' rule. The description only restates that constraint and adds no format, size, or resolution semantics (e.g. relative path base) beyond the 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?

States specific verbs (parse, type-check, verify) and a specific resource (an Assura contract), which is far more informative than the bare name. It does not, however, distinguish itself from assura_ir_verify or assura_infer, so an agent must guess which verification-adjacent sibling applies.

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?

"Provide either `source` or `file`" gives an input-selection rule but no when-to-use versus alternatives, no prerequisites, and no statement of what to do if neither is supplied. Usage is implied by the tool name and the word 'verify' rather than stated.

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

Deploy Server

Other Tools