Skip to main content
Glama

Market Brew

Get the authenticated Crew

get_current_crew
Read-onlyIdempotent

Use this when the user asks which Market Brew Crew is currently linked or selected. Returns only data visible to the linked Market Brew account.

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_current_crew"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A3.8/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 a closed-world scope, so safety behavior is covered. The description adds a useful scoping note that results are limited to what the linked account can see, but says nothing about the shape or limits of the returned data. That is a modest value-add, consistent with a 3 when annotations carry the safety profile.

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, zero filler, with the invocation trigger front-loaded before the data-visibility caveat. Nothing in it could be removed without losing meaning.

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 zero-parameter read with full annotation coverage and no output schema, the definition covers the trigger and the permission boundary. The one gap is that without an output schema it never hints at what fields a Crew record contains, leaving the agent to discover the return shape at call time.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the schema is effectively complete. Baseline 4 does not apply here because the description also offers no framing of what the parameterless call resolves to beyond 'current'; a neutral 3 reflects no gain and no loss.

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+resource combination — returns the Crew currently linked/selected for the authenticated Market Brew account — which is distinguishable from a generic get_crew lookup. It stops short of naming the sibling it contrasts with, so differentiation relies on the word 'current' alone.

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?

It states a concrete trigger: use when the user asks which Crew is currently linked or selected. That is a clear usage context, but there is no explicit when-not guidance or reference to an alternative such as get_crew for looking up a Crew by identifier.

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