Skip to main content
Glama
Sign In
stock-image-mcp

stock-image-mcp

by Hasilt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_rate_limit_status

Check remaining request quota for stock image providers before choosing where to run searches.

Instructions

Inspect remaining request quota per provider before deciding where to search.

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

Input Schema

NameRequiredDescriptionDefault
providerNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It states the action (inspect quota) but does not disclose whether the operation is read-only, consumes quota itself, or requires authentication. It leaves out important behavioral details that could affect usage, making it adequate but not comprehensive.

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?

The description is a single, front-loaded sentence with no wasted words. It efficiently states the tool's purpose and usage context.

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 simple tool with one optional parameter and an output schema, the description provides enough context for the agent to understand its role in the workflow. It might not cover all edge cases (e.g., null provider), but given the simplicity, it is nearly complete.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only hints at 'per provider' without explaining the parameter's possible values or the meaning of null/default. The description does not compensate for the schema's lack of parameter details, leaving provider semantics ambiguous.

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?

The description uses a specific verb 'Inspect' with a clear resource ('remaining request quota per provider') and distinguishes itself from sibling tools focused on searching/downloading images. It clearly states the tool's function of checking quota status.

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?

The phrase 'before deciding where to search' provides clear context for when to use the tool, but it does not explicitly mention alternatives or when not to use it. This is a clear usage guideline without exclusions.

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

Deploy Server

Other Tools