Skip to main content
Glama

arcat

by com.arcat
OverviewDiscussionsAdmin

Browse CSI Sections

browse_csi_sections
Read-onlyIdempotent

Browse CSI MasterFormat building product categories.

No parameters: list all divisions (e.g., "07 - Thermal and Moisture Protection"). Division only: list all entries under that division. Division + level: filter by hierarchy depth: Level 1 = Groups (e.g., 07 10 00 Dampproofing and Waterproofing) Level 2 = Sections (e.g., 07 21 00 Thermal Insulation) Level 3 = Narrowscope (e.g., 07 21 13 Board Insulation) Add section to drill into a specific parent (e.g., division "07", level 2, section "072000").

Input Schema

NameRequiredDescriptionDefault
levelNoHierarchy depth within division: 1=group, 2=section, 3=narrowscope
sectionNoParent section code to filter within (e.g., "072000" to see sections under Thermal Protection)
divisionNoCSI division code (e.g., "07"). Omit to list all divisions.

Output Schema

NameRequiredDescriptionDefault
totalYes
sectionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "sections": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "arcat_url": {
+            "type": "string"
+          },
+          "code": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "number"
+              }
+            ]
+          },
+          "division": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "number"
+              }
+            ]
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "arcat_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total",
+    "sections"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. Beyond that, the description discloses the filtering semantics (that output changes shape depending on which parameters are supplied) and the meaning of each hierarchy level, which is real behavioral context. It omits any note on result size or pagination, though an output schema exists.

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?

Front-loaded one-line purpose followed by a compact, scannable enumeration of parameter combinations. Every line adds distinct information; the inline examples clarify without padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A read-only hierarchical browse tool with full schema coverage and an output schema needs only the parameter-combination model, which the description fully supplies. Nothing an agent requires to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds cross-parameter semantics the schema cannot express: how division, level, and section compose to change the result set, plus a worked example ('07', level 2, '072000'). This goes beyond the per-field descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Browse CSI MasterFormat building product categories') and immediately explains the hierarchical model that defines the tool. The sibling tools (search_manufacturers, get_manufacturer, search_products) are in unrelated domains, so no sibling differentiation is required here.

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

Usage Guidelines4/5

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

Explicitly enumerates the four calling modes — no parameters (list divisions), division only, division + level, and section added to drill into a parent — which tells the agent exactly what each combination produces. It does not name alternatives or exclusions, but none of the siblings compete for this task.

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

All arcat toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources