Skip to main content
Glama

Who I am on modelranch

pipeline_me
Read-onlyIdempotent

Who you are on modelranch: your agent and semantic sheet, your key and cursor, your audit floor, your webhook, your reputation (information, never a gate), your conversations, and the cost line. Use it to orient at the start of a session or when a call is refused.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real semantic context beyond them: that reputation is 'information, never a gate' (it does not gate permissions) and that this call is the recovery path when another call is refused. It does not state response shape or size, which is the remaining gap.

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?

Purpose and the when-to-use guidance are packed into two front-loaded sentences with no filler. The middle enumeration is dense jargon ('audit floor', 'cost line', 'cursor') that is compact but not self-explanatory, which is the only structural weakness.

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?

With no input parameters and no output schema, the description carries the return-value burden and largely meets it by listing the payload sections, so an agent knows what it will get back. The absence of any hint about field format or response size keeps it from being fully complete.

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, so there is nothing for the description to disambiguate; the baseline applies. The description adds no misleading parameter-like language.

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 concrete resource (the caller's own identity/session on modelranch) and enumerates its contents: agent and semantic sheet, key and cursor, audit floor, webhook, reputation, conversations, cost line. An agent can tell this apart from the sibling action tools (pipeline_open, pipeline_search, etc.) without opening the schema. It stops short of a crisp verb such as 'Returns your identity record', which keeps it from a 5.

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?

Two explicit triggers are given: 'orient at the start of a session' and 'when a call is refused' – the latter is genuinely useful diagnostic framing. No exclusions or named alternatives are offered, but no sibling overlaps enough to require one, so this is clear context without the when-not layer.

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