Skip to main content
Glama

get_agent_steering

Read-onlyIdempotent

Reads workspace agent.md steering directives so AI coding agents can load persistent workspace rules before acting.

Instructions

Read the workspace agent.md steering directives.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety and repeatability are covered structurally. The description adds only the identity of the source file (agent.md steering directives). It says nothing about what happens when the file is absent, how large the content may be, or what format it comes back in.

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?

One short sentence with the object of the read front-loaded. Every word carries information and there is no boilerplate or repetition of the title.

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 simple parameterless read, annotations cover the safety profile, but the description never says what is returned (raw markdown text, parsed directives, or an empty result when agent.md does not exist). With no output schema present, that return-shape gap is the main missing piece an agent would want before calling.

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?

The tool takes zero parameters, which is the baseline-4 case. There is no parameter surface for the description to explain, and the empty schema matches the stated behavior of reading a single fixed workspace artifact.

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 and resource: read the workspace agent.md steering directives. That distinguishes it from siblings like get_canonical_template or get_workspace_status by naming the exact artifact it returns. It stops short of 5 because it doesn't state the return form or how it relates to those sibling reads.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. An agent must infer that this is the tool to call when it needs workspace steering context, and cannot tell from the text whether it should also call get_canonical_template alongside it.

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