Skip to main content
Glama

NETIM: agencja marketingu internetowego

Usługi NETIM

lista_uslug
Read-only

Lista usług agencji NETIM (SEO, GEO, Google Ads, Meta Ads, content, audyty, opieka nad stroną) z adresami stron.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered without description help. The description adds useful context that each entry includes a page address, but it says nothing about whether the returned list is static or filtered, ordering, or completeness — modest added value against an already-annotated read-only tool.

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?

A single front-loaded sentence that spends no words on preamble. The core purpose comes first and the parenthetical enumeration plus 'z adresami stron' each earn their place by defining scope and payload.

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-only catalog tool with no output schema, the description is nearly sufficient: it tells the agent what entities come back and that each carries a URL. It stops short of stating the response shape or count, but the complexity of the tool is low enough that this is a minor gap.

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 no per-parameter meaning to convey and the baseline of 4 applies. The description correctly implies no input is needed, consistent with the empty schema.

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?

Names a specific verb+resource ('Lista usług agencji NETIM') and enumerates the exact service categories returned (SEO, GEO, Google Ads, Meta Ads, content, audyty, opieka nad stroną), making the tool's scope unmistakable. It does not explicitly differentiate itself from the kontakt/szukaj siblings, which keeps it at 4 rather than 5.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for browsing the agency's service catalog rather than searching or getting contact data. There is no explicit when-to-use statement, no exclusion of alternatives, and no mention of how it complements szukaj or kontakt.

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