get_sulvo_signup_ads_txt
Run normal Sulvo signup step 4a: fetch the ads.txt lines the publisher must add for site ownership verification.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| userId | Yes | ||
| outputFormat | No | markdown |
TDQS
B3.1/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Only states it is a 'normal' fetch, but no details on side effects, idempotency, rate limits, or authentication requirements. Inadequate for a mutation-free read.
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?
Single sentence, front-loaded with key information. No redundant words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and minimal description, the agent lacks details on return format, error cases, and prerequisites. For a signup step, more context is needed for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, yet description adds no explanation for 'userId' or 'outputFormat'. The description does not link the parameters to the action, leaving the agent with no semantic help beyond the schema.
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?
Clearly states the verb 'fetch' and resource 'ads.txt lines', and provides context as step 4a of signup. Distinguishes from sibling 'verify_sulvo_signup_ads_txt' which presumably verifies instead of fetching.
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?
Implies it is a step in the signup process, but does not explicitly state when to use vs. alternatives nor provide exclusion criteria. Needs more guidance on sequence or conditions.
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.
TDQS
C2.7/5.0
Disambiguation3/5
Many tools are clearly scoped (e.g., `create_sulvo_ad_unit` vs `delete_sulvo_ad_unit`), but there is confusion with tools like `run_publisher_revenue_audit` and `get_publisher_revenue_audit_checklist` which sound like they could overlap. Also, `start_sulvo_signup` and `create_sulvo_signup_account` seem to operate on different stages of signup but could be confused at a glance.
Naming Consistency4/5
The naming convention is generally consistent with a `verb_sulvo_noun` pattern (e.g., `create_sulvo_ad_unit`, `delete_sulvo_ad_unit`). The `get_` and `run_` prefixes are used somewhat inconsistently (e.g., `run_publisher_revenue_audit` vs `get_publisher_revenue_audit_checklist`), and some tool names feel a bit verbose, but overall patterns are recognizable.
Tool Count3/5
With 40 tools, the server covers a massive surface area including signup, activation, reporting, and auditing. While each tool has a specific purpose, the number feels somewhat bloated for a single server, suggesting it could be split into more focused sub-servers (e.g., `sulvo-signup`, `sulvo-reporting`). It is on the high end of 'appropriate'.
Completeness4/5
The tool set appears very complete for the Sulvo ecosystem, covering everything from account creation (`create_sulvo_signup_account`) to auditing (`run_agentic_readiness_audit`) and activation (`submit_sulvo_activation_workspace`). The only minor gap is the lack of a direct way to start signup beyond step 1, but this is documented as an API limitation, not a tool gap.