Skip to main content
Glama

BRAINIAC Structural Engineering Calculators

Column tributary areas and load takedown

structural-calcs_tributary-load-takedown
Read-onlyIdempotent

Tributary areas on a rectangular grid (or caller polygons) with cumulative dead/live takedown over floors. Price $0.02 USDC. POST /api/v1/structural-calcs/tributary-load-takedown. An unpaid call returns the x402 payment terms and does not run.

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": {
      "floors": "<floors>"
    },
    "name": "structural-calcs_tributary-load-takedown"
  }
}

Input Schema

NameRequiredDescriptionDefault
gridXNogridX, array. Optional.
gridYNogridY, array. Optional.
floorsYesfloors, array. Required.
columnsNocolumns, array. Optional.
factorsNofactors, value. Optional.
omittedColumnsNoomittedColumns, array. Required.

Output Schema

NameRequiredDescriptionDefault
columnsNocolumns. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld. The description adds genuinely valuable context beyond them: a $0.02 USDC price, the POST endpoint, and that an unpaid call returns x402 payment terms without running. This is useful behavioral disclosure not captured by the annotations.

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?

Three tight sentences, front-loaded with purpose, followed by payment and failure behavior. No waste, though the endpoint path and price could be considered slightly separable details.

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 6-parameter tool with 100% schema coverage and an output schema, the description is complete enough: purpose, payment, and unpaid-call behavior are covered. Return values are handled by the output schema, so nothing critical is missing.

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 effectively 100%, so the schema already carries parameter meaning. The description only hints that gridX/gridY can be replaced by caller polygons; it adds little syntax or format detail beyond the schema, so baseline 3 applies.

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 first sentence names specific verbs and resources: tributary areas on a grid or caller polygons with cumulative dead/live takedown over floors. It is clear what the tool computes, though it does not explicitly distinguish itself from the other structural-calc siblings.

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 specific purpose (a tributary-area/load-takedown calculation), but there is no explicit when-to-use or when-not guidance and no named alternative. The agent can infer applicability but must reason about it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources